Release 10.5.0-rc7
RC7
-
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 10.5" using this Merged MRs list -
Check the following list of critical issues/MRs which are to be included in 10.5.0
. Where appropriate, ensure each has made it into both CE and EE-
REFERENCE_TO_MR_TO_PICK
-
-
Follow the [Creating subsequent RCs] guide for
10.5.0-rc7
:-
If you didn't merge CE into EE in the preparation branches, or if the CE stable branch had additional commits, merge CE 10-5-stable
into EE10-5-stable-ee
following the Merging a CE stable branch into its EE counterpart guide. (In general this should be unnecessary.) -
Ensure builds are green on Omnibus CE stable branch and Omnibus EE stable branch -
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. Builds should fail if this is needed.) -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v10.5.0-rc6-ee..10-5-stable-ee -- db/migrate db/post_migrate
=> -
In #releases
: I'm going to tag10.5.0-rc7
-
Tag the 10.5.0-rc7
version using therelease
task:# In the release-tools project: bundle exec rake "release[10.5.0-rc7]"
-
-
Check progress of EE packages build and CE packages build -
Get confirmation from a production team member to deploy staging. Use !oncall prod
if needed to find who's on call. -
On video call, deploy release 10.5.0-rc7
to staging.gitlab.comsh # In the takeoff project: bin/takeoff-deploy -e staging -v 10.5.0-rc7-ee.0
-
Share the output of the migrations from the takeoff script in this issue via a snippet. Flag any migrations that take more than 5 minutes to run. -
Announce on the #releases
Slack channels:10.5.0-rc7
has been deployed to staging. Blog post draft: MERGE_REQUEST_URL -
Create a "QA Task" issue in the gitlab-org/release/tasks repo. -
Wait for the QA Task deadline to pass. -
Get confirmation from a production team member to deploy canary. Use !oncall prod
if needed to find who's on call. -
On video call, deploy release 10.5.0-rc7
to canary.gitlab.comsh # In the takeoff project: bin/takeoff-deploy -e canary -v 10.5.0-rc7-ee.0
-
Get confirmation from a production team member to deploy production. Use !oncall prod
if needed to find who's on call. -
If downtime is expected, publicly [announce the deployment] on Twitter and with the GitLab.com deploy alert banner in the #production
channel, 1 hour in advance!broadcast --start X:Y --end A:B "We will deploying GitLab EE 10.5.0-rc7 starting at X:Y. GitLab will be unavailable for Z minutes. For status updates, please follow https://twitter.com/GitLabStatus"
!tweet "We will be deploying GitLab EE 10.5.0-rc7 starting at X:Y UTC, 15 mins of downtime expected"
-
On video call, deploy release 10.5.0-rc7
to GitLab.comsh # In the takeoff project: bin/takeoff-deploy -e production -v 10.5.0-rc7-ee.0
-
If downtime was an issue, tweet in the #production
channel that the deployment has finished:!tweet "GitLab EE 10.5.0-rc7 has been deployed."
-
Take notes of the time it took for the migrations to complete on the deployment to production. # On the takeoff repo bundle exec rake "follow_migrations[production]"
-
Post a [tweet about] the 10.5.0-rc7
release in the#releases
channel:!tweet "GitLab 10.5.0-rc7 is available: https://packages.gitlab.com/gitlab/unstable This is a release candidate, we'll release 10.5 on the 22nd of this month."
For references:
On gitlab.com
- https://gitlab.com/gitlab-org/gitlab-ce/commits/10-5-stable
- https://gitlab.com/gitlab-org/gitlab-ee/commits/10-5-stable-ee
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/10-5-stable
- https://gitlab.com/gitlab-org/omnibus-gitlab/commits/10-5-stable-ee
On gitlab.org