Release 9.4.2
-
Cherry-pick merge requests labeled [ Pick into Stable
] for the current milestone (you can take advantage of thePick into Stable
9.4 merged merge requests page) into the CE9-4-stable
and EE9-4-stable-ee
branches, respectively. -
Check the following list of critical issues/MRs which are to be included in 9.4.2
. Ensure each has made both CE and EE -
Merge CE 9-4-stable
into EE9-4-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.4.1-ee..9-4-stable-ee -- db/migrate db/post_migrate
=> -
Check omnibus-gitlab/9-4-stable
CHANGELOG.md -
Check omnibus-gitlab/9-4-stable-ee
CHANGELOG.md -
While waiting for tests to be green, now is a good time to start on the blog post: BLOG_POST_MR -
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.4.2
-
Tag the 9.4.2
version using therelease
task:
# In the release-tools project:
bundle exec rake "release[9.4.2]"
-
Check progress of EE packages build and CE packages build -
In #production
: I'm going to deploy9.4.2
to staging -
On video call, deploy release 9.4.2
to staging.gitlab.com
# In the takeoff project:
bundle exec rake "deploy[staging, 9.4.2-ee.0]"
-
In #production
: I'm going to deploy9.4.2
to canary -
On video call, deploy release 9.4.2
to canary.gitlab.com
# In the takeoff project:
bundle exec rake "deploy[canary, 9.4.2-ee.0]"
-
In #production
: I'm going to deploy9.4.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.4.2
to GitLab.com
# In the takeoff project:
bundle exec rake "deploy[production, 9.4.2-ee.0]"
-
From the build pipeline, manually publish public packages -
Verify that packages appear on packages.gitlab.com
: EE / CE -
Verify that Docker images appear on hub.docker.com
: EE / CE -
Create the 9.4.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.4.2 is released! BLOG_POST_URL DESCRIPTION OF THE CHANGES
- In the 9.4 Regressions issue:
-
Add the following notice:
-
`9.4.2` has been tagged, further fixes will go into `9.4.3` as necessary.
-
Remove notes for the regressions fixed by version 9.4.2
-
Add omnibus-gitlab/9.4.2+ce.0
CHANGELOG.md items toomnibus-gitlab/master
CHANGELOG.md
For references:
Edited by James Edwards-Jones