Feature Release Process¶
This document describes the process for creating a major or minor feature release of Cilium.
On Freeze date¶
Fork a new release branch from master:
git checkout master; git pull git checkout -b v1.2 git push
Protect the branch using the GitHub UI to disallow direct push and require merging via PRs with proper reviews.
Replace the contents of the
CODEOWNERSfile with the following to reduce code reviews to essential approvals:
* @cilium/janitors api/ @cilium/api pkg/apisocket/ @cilium/api pkg/monitor/payload @cilium/api pkg/policy/api/ @cilium/api pkg/proxy/accesslog @cilium/api
Commit changes, open a pull request against the new
v1.2branch, and get the pull request merged
git checkout -b pr/prepare-v1.2 git add [...] git commit git push
Follow the Release Candidate Process to release
Create the following GitHub labels:
Prepare the master branch for the next development cycle:
git checkout master; git pull
VERSIONfile to contain
git addand create & merge a PR titled
Prepare for 1.3.0 development.
- Update the release branch on
Jenkins to be tested on every change and Nightly.
(Only 1.0 minor releases) Tag newest 1.0.x Docker image as
v1.0-stableand push it to Docker Hub. This will ensure that Kops uses latest 1.0 release by default.