Commit 05eb22448604b784811bd6a1c8c1db599bf4b6b4
1 parent
5b123dbf
Exists in
spb-stable
and in
3 other branches
Add patch release document.
Showing
1 changed file
with
23 additions
and
0 deletions
Show diff stats
| @@ -0,0 +1,23 @@ | @@ -0,0 +1,23 @@ | ||
| 1 | +# Things to do when doing a patch release | ||
| 2 | +NOTE: This is a guide for GitLab developers. If you are trying to install GitLab see the latest stable [installation guide](install/installation.md) and if you are trying to upgrade, see the [upgrade guides](update). | ||
| 3 | + | ||
| 4 | +## When to do a patch release | ||
| 5 | + | ||
| 6 | +Do a patch release when there is a critical regression that needs to be adresses before the next monthly release. | ||
| 7 | +Otherwise include it in the monthly release and note there was a regression fix in the release announcement. | ||
| 8 | + | ||
| 9 | +## Release Procedure | ||
| 10 | + | ||
| 11 | +1. Verify that the issue can be repoduced | ||
| 12 | +1. Create an issue on private GitLab development server | ||
| 13 | +1. Name the issue "Release X.X.X CE and X.X.X EE", this will make searching easier | ||
| 14 | +1. Fix the issue on a feature branch, do this on the private GitLab development server | ||
| 15 | +1. After the branch is merged into master, cherry pick the commit(s) into the current stable branch | ||
| 16 | +1. In a separate commit in the stable branch, update the VERSION and CHANGELOG | ||
| 17 | +1. Create an annotated tag vX.X.X for CE and another patch release for EE | ||
| 18 | +1. Make sure that the build has passed and no tests are failing | ||
| 19 | +1. Push the code and the tags to all the CE and EE repositories | ||
| 20 | +1. Apply the patch to GitLab Cloud and the private GitLab development server | ||
| 21 | +1. Send tweets about the release from @gitlabhq, tweet should include the most important feature that the release is addressing as well as the link to the changelog | ||
| 22 | +1. Build new packages with the latest version | ||
| 23 | + |