kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/doc/release/patch.md

2.3 KiB
Raw Blame History

Things to do when doing a patch release

NOTE: This is a guide for GitLab developers. If you are trying to install GitLab see the latest stable installation guide and if you are trying to upgrade, see the upgrade guides.

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.

Release Procedure

Preparation

  1. Verify that the issue can be reproduced
  2. Note in the 'GitLab X.X regressions' that you will create a patch
  3. Create an issue on private GitLab development server
  4. Name the issue "Release X.X.X CE and X.X.X EE", this will make searching easier
  5. Fix the issue on a feature branch, do this on the private GitLab development server
  6. If it is a security issue, then assign it to the release manager and apply a 'security' label
  7. Build the package for GitLab.com and do a deploy
  8. Consider creating and testing workarounds
  9. After the branch is merged into master, cherry pick the commit(s) into the current stable branch
  10. Make sure that the build has passed and all tests are passing
  11. In a separate commit in the stable branch update the CHANGELOG
  12. 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"

Bump version

Get release tools

git clone git@dev.gitlab.org:gitlab/release-tools.git
cd release-tools

Bump version in stable branch, create release tag and push to remotes:

bundle exec rake release["x.x.x"]

Or if you need to release only EE:

CE=false be rake release['x.x.x']

Release

  1. Apply the patch to GitLab Cloud and the private GitLab development server
  2. Build new packages with the latest version
  3. Cherry-pick the changelog update back into master
  4. Create and publish a blog post
  5. Send tweets about the release from @gitlabhq, tweet should include the most important feature that the release is addressing and link to the blog post
  6. Note in the 'GitLab X.X regressions' issue that the patch was published (CE only)