Release 9.5.2
CE Prep MR: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/13816 EE Prep MR: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2757
-
Create preparation MRs by following the instructions in release-tools. -
Cherry-pick changes into preparation MRs following their instructions -
Cherry-pick remaining merge requests labeled Pick into Stable
for the current milestone using thePick into Stable
9.5 merged merge requests page -
Check for merge requests marked Pick into Backports
and cherry-pick those which should go into this release. -
Check the following list of critical issues/MRs which are to be included in 9.5.2
. Where appropriate, ensure each has made it into both CE and EE-
REFERENCE_TO_MR_TO_PICK
-
-
Merge CE 9-5-stable
into EE9-5-stable-ee
following the [Merging a CE stable branch into its EE counterpart] guide -
Sync stable branches: CE, EE, and Omnibus to dev
, CE and Omnibus togithub
-
Sync master branches to dev
andgithub
, as the CHANGELOG will be automatically updated on master during tagging -
If needed, sync tags for dependencies ( gitlab-shell
,gitlab-workhorse
,gitlab-pages
,gitaly
) todev
andgithub
(when applicable) -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.5.1-ee..9-5-stable-ee -- db/migrate db/post_migrate
=> -
While waiting for tests to be green, now is a good time to start on the blog post: gitlab-com/www-gitlab-com!7275 (merged) -
Ensure tests are green on CE stable branch -
Ensure tests are green on EE stable branch -
Ensure tests are green on Omnibus CE stable branch -
Ensure tests are green on Omnibus EE stable branch -
In #releases
: I'm going to tag9.5.2
-
Tag the 9.5.2
version using therelease
task:```sh # In the release-tools project: bundle exec rake "release[9.5.2]" ```
-
Check progress of EE packages build and CE packages build -
In #production
: I'm going to deploy9.5.2
to staging -
On video call, deploy release 9.5.2
to staging.gitlab.comsh # In the takeoff project: bundle exec rake "deploy[staging, 9.5.2-ee.0]"
-
In #production
: I'm going to deploy9.5.2
to canary -
On video call, deploy release 9.5.2
to canary.gitlab.comsh # In the takeoff project: bundle exec rake "deploy[canary, 9.5.2-ee.0]"
-
In #production
: I'm going to deploy9.5.2
to production -
Make sure to announce the deploy on Twitter and GitLab.com - With downtime: 1 hour before
- Without downtime: 15 minutes before
-
On video call, deploy release 9.5.2
to GitLab.comsh # In the takeoff project: bundle exec rake "deploy[production, 9.5.2-ee.0]"
-
Create the 9.5.2
version on https://version.gitlab.com -
Deploy the blog post -
Tweet (prepare the Tweet text below or paste the tweet URL instead): ``` GitLab 9.5.2 is released! BLOG_POST_URL DESCRIPTION OF THE CHANGES ```
-
In the 9.5 Regressions issue:
-
Add the following notice: `9.5.2` has been tagged, further fixes will go into `9.5.3` as necessary.
-
Remove notes for the regressions fixed by version 9.5.2
-
-
Add omnibus-gitlab/9.5.2+ce.0
CHANGELOG.md items toomnibus-gitlab/master
CHANGELOG.md
For references: