...
- alpha releases up to the M3 milestone: rx.1 through rx.m (with first alpha release: r0.1)
- release-candidates between the M3 and the M4 milestone: rx.m+1 through rx.n
- finishing with the public-release for inclusion in the meta-release: rx.n+1
- maintenance-releases (for MINOR and PATCH updates) after public release: rx.n+2 and up
- next release (for MAJOR updates): same as above, starting at rx+1.0
Example for a non-breaking update of a public-release API version 1.0.0, resulting in a new release with API version 1.1.0:
- Develop the 1.1.0 update on the main branch. The first PR updates the version to wip, and the URL to contain vwip.
- Once sufficiently stable, update the new API version to 1.1.0-alpha.1.
- Several intermediate alpha API versions may be created.
- Then one or more intermediate release-candidate API versions may be created.
- The last release-candidate API version will be proposed for meta-release.
- For meta-release approval, create the PR for the new public-release API version 1.1.0.
- After meta-release approval, create the release for the new public-release API version 1.1.0, with its release tag rx+1.n and release package ("latest")).