A version lifecycle moves an API version through Preview, Current, Deprecated, and Deleted states, balancing rapid delivery against compatibility and maintenance costs. section 24.3.2
Use each state with a deliberately narrow change policy:
- Preview permits all changes while functionality remains unstable and users accept possible breakage. section 24.3.2
- Current freezes the version except for mandatory changes and critical bug fixes, protecting client code. section 24.3.2
- Deprecated marks a former Current version for impending removal under a deprecation policy. section 24.3.2
- Deleted removes or makes the deprecated version inaccessible. section 24.3.2
Sliding-window API releases
Version 1 starts as Preview in January, becomes Current in February, Deprecated in March, and Deleted in May. Meanwhile, newer versions progress through the same sequence, keeping feature work moving without modifying the stable version. section 24.3.2
Table 24.1 Overview of different version states (view table figure)
Compare the four lifecycle states with their descriptions and permitted changes. section 24.3.2





