whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify deprecation rule 3

Browse Source
This commit is contained in:
Jordan Liggitt
2022-01-18 10:12:19 -05:00
parent b599a32374
commit 3dfffd39c8
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/reference/using-api/deprecation-policy.md
+4 -4
View File
@@ -73,11 +73,11 @@ knows how to convert between them in both directions. Additionally, any new
field added in v2 must be able to round-trip to v1 and back, which means v1 field added in v2 must be able to round-trip to v1 and back, which means v1
might have to add an equivalent field or represent it as an annotation. might have to add an equivalent field or represent it as an annotation.
**Rule #3: An API version in a given track may not be deprecated until a new **Rule #3: An API version in a given track may not be deprecated in favor of a less stable API version.**
API version at least as stable is released.**
GA API versions can replace GA API versions as well as beta and alpha API * GA API versions can replace beta and alpha API versions.
versions. Beta API versions *may not* replace GA API versions. * Beta API versions can replace earlier beta and alpha API versions, but *may not* replace GA API versions.
* Alpha API versions can replace earlier alpha API versions, but *may not* replace GA or beta API versions.
**Rule #4a: Other than the most recent API versions in each track, older API **Rule #4a: Other than the most recent API versions in each track, older API
versions must be supported after their announced deprecation for a duration of versions must be supported after their announced deprecation for a duration of