2018-01-11: lbennett 10.4.0-rc3 release task
Release manager daily tasks
Tasks
CE to EE merges
-
Daily merge 1 assigned to lbennett https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3994 https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4023/ -
Daily merge 2 assigned to AMERICA_OR_CALA_BASED_PERSON LINK_TO_MR
Creating release
-
10.4.0-rc3
10.4: https://gitlab.com/gitlab-org/gitlab-ce/issues/41629
CE rc3 prep: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16334
EE rc3 prep: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3980
-
10.4.0-rc4
10.4: https://gitlab.com/gitlab-org/gitlab-ce/issues/41629
CE rc4 prep: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16400
EE rc4 prep: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/4029
QA
-
QA task 1 assigned to lbennett #23 (closed) -
QA task 2 assigned to PERSON LINK_TO_ISSUE -
QA task 2 assigned to PERSON LINK_TO_ISSUE
Deployment
-
Deploy 10.4.0-rc3 to staging.gitlab.com (link optional) -
Deploy 10.4.0-rc3 to canary.gitlab.com (link optional) -
Deploy 10.4.0-rc3 to gitlab.com (link optional)
Escalations
CE to EE merges
Asked FE to join in resolving Thursdays conflicts.
Creating release
Marin reviewed the rc3 prep branches and merged them.
Realised rc3 has #12 (closed) in it, after release, which we didn't want. Decided to continue and make rc4 the fix and another icky CI migration.
Deployment
(Write down any escalation paths you needed to take for deploy and why.) (Eg. Production deploy was aborted so escalated to X, environment was not ready, etc.)
QA
(Write down any escalation paths you needed to take for deploy and why.) (Eg. QA task 1 was not completed in time so escalated to X.)
Remarks
CE to EE merges
Wednesday is still not merged
Thursday came in with a lot of conflicts, but FE banded together to get them done swiftly, we even had a reoccurring call halfway through!. Had some issues with failures after that, but getting it cleared up whilst releasing rc3.
Creating release
Marin spotted that we had a merge commit with an exception request in the prep branches, so we reverted that to be safe.
The missing commits got merged into prep branches. Going to merge stable branches once prep branches are merged and starting with rc3 release.
rc3 migrations diff: https://gitlab.com/gitlab-org/gitlab-ce/snippets/1692709
Started on rc4.
QA
(Write down any observations, blockers and challenges encountered during any of the QA tasks.) (Create the issue and link here. Link if issue exists already.)
Deployment
(Write down any observations, blockers and challenges encountered during any deploy.) (Create the issue and link here. Link if issue exists already.)
Used time
CE to EE merge tasks
Resolving thursday conflicts: ~1 hour
Release tasks
Fixing missed commits rc3: ~40 minutes
Merging stables: ~15 minutes
Picking into rc4: ~30 minutes (only because I realised I released something early, see "escalations" for release tasks in this issue)
QA
(Estimated time spent on release tasks.) (Note down total time from the moment QA task could have been carried out until QA was completed.)
Deployment
Deploying 10.4.0-rc3.ee.0 to staging: ~30 minutes