Things to do when doing a patch release
When to do a patch release
Do a patch release when there is a critical regression that needs to be addresses before the next monthly release.
Otherwise include it in the monthly release and note there was a regression fix in the release announcement.
- Verify that the issue can be reproduced
- Note in the 'GitLab X.X regressions' that you will create a patch
- Create an issue on private GitLab development server
- Name the issue "Release X.X.X CE and X.X.X EE", this will make searching easier
- Fix the issue on a feature branch, do this on the private GitLab development server
- If it is a security issue, then assign it to the release manager and apply a 'security' label
- Consider creating and testing workarounds
- After the branch is merged into master, cherry pick the commit(s) into the current stable branch
- Make sure that the build has passed and all tests are passing
- In a separate commit in the master branch update the CHANGELOG
- For EE, update the CHANGELOG-EE if it is EE specific fix. Otherwise, merge the stable CE branch and add to CHANGELOG-EE "Merge community edition changes for version X.X.X"
- Merge CE stable branch into EE stable branch
Get release tools
git clone email@example.com:gitlab/release-tools.git cd release-tools
Bump all versions in stable branch, even if the changes affect only EE, CE, or CI. Since all the versions are synced now, it doesn't make sense to say upgrade CE to 7.2, EE to 7.3 and CI to 7.1.
Create release tag and push to remotes:
bundle exec rake release["x.x.x"]
- Build new packages with the latest version
- Apply the patch to GitLab.com and the private GitLab development server
- Apply the patch to ci.gitLab.com and the private GitLab CI development server
- Create and publish a blog post, see patch release blog template
- Send tweets about the release from
@gitlab, tweet should include the most important feature that the release is addressing and link to the blog post
- Note in the 'GitLab X.X regressions' issue that the patch was published (CE only)
- Create the 'x.y.0' version on version.gitlab.com
- Create new AMIs
- Create a new patch release issue for the next potential release