summaryrefslogtreecommitdiff
path: root/api_changes.md
diff options
context:
space:
mode:
authorTim Hockin <thockin@google.com>2015-07-17 15:35:41 -0700
committerTim Hockin <thockin@google.com>2015-07-17 15:35:43 -0700
commitda3e5f056b57f17ae5234085a00e792adaa02d57 (patch)
tree353b03851fb5203964fa04e0ed33c9391e27097f /api_changes.md
parent3e224d662c4fa605341cb6c57d98dcb143e6b2ae (diff)
Run gendocs
Diffstat (limited to 'api_changes.md')
-rw-r--r--api_changes.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/api_changes.md b/api_changes.md
index edf227cc..7a0418e8 100644
--- a/api_changes.md
+++ b/api_changes.md
@@ -30,6 +30,7 @@ Documentation for other releases can be found at
<!-- END STRIP_FOR_RELEASE -->
<!-- END MUNGE: UNVERSIONED_WARNING -->
+
# So you want to change the API?
The Kubernetes API has two major components - the internal structures and
@@ -365,6 +366,7 @@ $ hack/update-swagger-spec.sh
The API spec changes should be in a commit separate from your other changes.
## Incompatible API changes
+
If your change is going to be backward incompatible or might be a breaking change for API
consumers, please send an announcement to `kubernetes-dev@googlegroups.com` before
the change gets in. If you are unsure, ask. Also make sure that the change gets documented in