Release 10.8.0-rc6
Preparation
-
Create preparation MRs for this version and add the links below: # In the release-tools project: bundle exec rake "patch_merge_request[10.8.0-rc6]"
-
Cherry-pick changes into preparation MRs following their instructions -
Ensure the CE preparation MR has been fully merged into the EE counterpart -
Cherry-pick ~"Pick into 10.8" MRs for omninus-gitlab
-
Ensure the CE stable branch for omnibus-gitlab
has been fully merged into the EE stable branch -
Merge the preparation branches -
Cherry-pick remaining merge requests labeled ~"Pick into 10.8" -
Check the following list of critical issues/MRs which are to be included in
10.8.0-rc6
. Ensure each has made both CE and EE:-
gitlab-org/gitlab-ce!18844
-
-
Ensure builds are green on Omnibus CE stable branch and Omnibus EE stable branch
Packaging
-
Sync stable branches for CE, EE, and Omnibus to dev
; CE and Omnibus togithub
. -
Tag the 10.8.0-rc6
version using therelease
task:# In the release-tools project: bundle exec rake "release[10.8.0-rc6]"
-
Check for any problematic migrations in EE, and paste the diff in a snippet: git diff -M v10.8.0-rc6-ee..10-8-stable-ee -- db/migrate db/post_migrate ee/db/migrate ee/db/post_migrate
=> -
Check progress of EE packages build and CE packages build - This might take a while (around 80 min).
- We only need the EE packages to finish to continue with next steps.
Deploy
Deploys to production require confirmation from a production team member before
proceeding. Use !oncall prod
in the #production
channel to find who's on
call and ping someone. Deploys to staging or canary can be done at will, just
mention it in the #production
channel.
-
Warm up the packages on takeoff by running: # In the takeoff project: bin/takeoff-deploy -v 10.8.0-rc6.ee.0 -w
staging.gitlab.com
-
Notify #production that you're about to deploy on staging -
On video call, deploy 10.8.0-rc6
to staging.gitlab.com# In the takeoff project: bin/takeoff-deploy -e staging -v 10.8.0-rc6.ee.0
-
Comment with the output of the migrations from the takeoff script in this issue
QA
-
Announce with an @product-team
mention in the#product
Slack channel:@product-team `10.8.0-rc6` has been deployed to staging.
-
Create a "QA Task" issue in the gitlab-org/release/tasks repo, using the RC1-QA-task
template. #197 (closed) -
Notify #development and #releases about the QA issue with the following message: 10.8.0-rc6 has been deployed to staging, you can do QA and report any problems to the QA issue <link to the QA issue>
-
Wait for the QA Task deadline to pass
canary.gitlab.com
-
Notify #production that you're about to deploy on canary -
On video call, deploy 10.8.0-rc6
to canary.gitlab.com# In the takeoff project: bin/takeoff-deploy -e canary -v 10.8.0-rc6.ee.0
gitlab.com (production)
-
Get confirmation from a production team member to deploy production. If someone besides the oncall confirms, @mention
the oncall so they are aware. -
On video call, deploy 10.8.0-rc6
to GitLab.com# In the takeoff project: bin/takeoff-deploy -e production -v 10.8.0-rc6.ee.0
Release
-
Post a tweet about the 10.8.0-rc6
release in the#releases
channel:!tweet "GitLab 10.8.0-rc6 is available: https://packages.gitlab.com/gitlab/unstable This is a release candidate, we'll release 10.8 on the 22nd of this month."