As of the 1.6 release, the Spinnaker team is committed to providing a more regular release cadence in order to help users understand when new features will be available, as well help non-core developers plan to get their features released in the next stable version of Spinnaker.
Every eight weeks we open the Release Window, meaning that we cut release
branches for the upcoming release. If the version we intend to release is
M.N, a branch with the name
release-M.N.x is cut in each component
repository. For example, see the state of the
Clouddriver repository leading up
to the 1.6 release:
We call this snapshot of all the Spinnaker repositories the “Release Candidate”.
Running the Release Candidate
Once these release branches are cut, anyone can run the release candidate using
# this would be version 'release-1.6.x-latest-unvalidated' for 1.6 hal config version edit --version release-M.N.x-latest-unvalidated hal deploy apply
Patching the Release Candidate
Do not merge feature code into a release branch, only fixes are accepted.
If you’ve found a fix for a bug in the Release Candidate, follow the patching procedure described here. If your patch is merged before the Release Window is closed, it will be included in this release.
Unless a severe error (e.g. security vulnerability, large-scale breakage) has a pending patch, patch releases are published at a weekly cadence on a best-effort basis.
Closing the Release Window
Once the community has deemed that the Candidate is “stable” (meaning all
passing, and no known issues or regressions remain), we will release Spinnaker
M.N.0. Further patches can be merged into the release branch for
future patch releases (e.g.
Upcoming Release Windows
Keep in mind, when the window opens, the release candidate becomes available. The actual release happens one to two weeks later.