Release 9.3.5
Preperation MRs:
- CE https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/12614
- EE https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/2327
-
Cherry-pick merge requests labeled [ Pick into Stable
] for the current milestone (you can take advantage of thePick into Stable
9.3 merged merge requests page) into the CE9-3-stable
and EE9-3-stable-ee
branches, respectively.-
REFERENCE_TO_MR_TO_PICK
-
-
Merge CE 9-3-stable
into EE9-3-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)-
gitlab-monitor
had a version update, check if anything is needed for this
-
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v9.3.4-ee..9-3-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!6689 (merged) -
Ensure blog post includes MYSQL TRIGGER
documentation as noted below at https://gitlab.com/gitlab-org/gitlab-ce/issues/34660#note_34181027
-
-
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.3.5
-
Tag the 9.3.5
version using therelease
task:```sh # In the release-tools project: bundle exec rake "release[9.3.5]" ```
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE / CE -
In #production
: I'm going to deploy9.3.5
to staging -
On video call, deploy release 9.3.5
to staging.gitlab.comsh # In the chef-repo project: bundle exec rake "deploy[staging, 9.3.5-ee.0]"
-
In #production
: I'm going to deploy9.3.5
to canary -
On video call, deploy release 9.3.5
to canary.gitlab.comsh # In the chef-repo project: bundle exec rake "deploy[canary, 9.3.5-ee.0]"
-
In #production
: I'm going to deploy9.3.5
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.3.5
to GitLab.comsh # In the chef-repo project: bundle exec rake "deploy[production, 9.3.5-ee.0]"
-
Create the 9.3.5
version on https://version.gitlab.com -
Deploy the blog post -
Tweet (prepare the Tweet text below or paste the tweet URL instead): ``` GitLab 9.3.5 is released! BLOG_POST_URL DESCRIPTION OF THE CHANGES ```
-
In the 9.3 Regressions issue:
-
Add the following notice: `9.3.5` has been tagged, further fixes will go into `9.3.6` as necessary.
-
Remove notes for the regressions fixed by version 9.3.5
-
-
Add omnibus-gitlab/9.3.5+ce.0
CHANGELOG.md items toomnibus-gitlab/master
CHANGELOG.md
For references: