Release 8.6
29th: (16 working days before the 22nd)
-
Triage the Omnibus milestone
16th: (4 working days before the 22nd)
-
Ensure omnibus-gitlab
is ready to build packages by asking the Omnibus maintainers -
Follow the Creating RC1 guide:
-
Update the "Installation from Source" guide -
Create the Update guides -
Merge GitLab CE into EE via merge request: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/256, https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/262, gitlab-org/gitlab-ee!269 -
In #operations
(be sure to mention people than can deploy to GitLab.com):I am starting the release tasks for `8.6.0-rc2` (LINK_TO_THIS_ISSUE). Will anyone be available to deploy it to GitLab.com when the packages are built?
-
In #development
:TL;DR: Ensure the 8.6 milestone and the `Pick to Stable` label are set, no need to ping me `8.6.0-rc2` was tagged (rc1 was tagged before the Git vulnerability “fix”) and deployed today. Since it’s a late 8.6 RC (due to late 8.5 patch releases), I will still merge master into stable until tomorrow but please already start to follow the "Change for stable release" process: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#changes-for-stable-releases Looking forward to merging/picking all your cool stuff in 8.6.0!
-
Tag and build (this is CI-automatized) the 8.6.0-rc2
version using therelease
task:bundle exec rake "release[8.6.0-rc2]"
-
-
Create the regression issue in the CE issue tracker using the regression_issue
task and bookmark it:bundle exec rake "regression_issue[8.6.0]"
-
Check that packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Update GitLab.com with 8.6.0-rc2
(this was a mess, see gitlab-com/operations#135 (closed)) -
Tweet about the 8.6.0-rc2
release:GitLab 8.6.0-rc2 is available: https://packages.gitlab.com/gitlab/unstable Use at your own risk. Please link regressions issues from https://gitlab.com/gitlab-org/gitlab-ce/issues/14303
-
Prepare the blog post using the new_release_post
task, in thewww-gitlab-com
project:rake new_release_post["8.6"]
-
Determine QA person and notify this person: @kelvinmutuma
Anytime beetween 17th (3 working days before the 22nd) and 21st (1 working day before the 22nd)
Copy-paste the tasks below for any other RCs (be sure to update the RC number).
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of the Dashboard > Merge Requests page) into the CE8-6-stable
and EE8-6-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.6.0-rc3
(be sure to use the correct RC number):-
Merge CE 8-6-stable
into EE8-6-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Tag and build (this is CI-automatized) the 8.6.0-rc3
version using therelease
task:bundle exec rake "release[8.6.0-rc3]"
-
-
Check that packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Update GitLab.com with 8.6.0-rc3
-
Tweet about the 8.6.0-rc3
release:GitLab 8.6.0-rc3 is available: https://packages.gitlab.com/gitlab/unstable Use at your own risk. Please link regressions issues from LINK_TO_REGRESSION_ISSUE
17th: (3 working days before the 22nd)
-
Do QA and fix anything coming out of it: https://gitlab.com/gitlab-org/gitlab-ce/issues/14355 -
Check that everyone is mentioned on the blog post using @all
:Hello @all, this is the monthly release post that will go out on the 22nd, announcing the new GitLab version. Look through it to see if we can make any changes and feel free to comment with suggestions or questions!
or, if the blog post is still very much a work in progress:
Hello @all, this is the merge request for the monthly release post that will go out on the 22nd, announcing the new GitLab version. Right now it's all boilerplate, but feel free to remind us about things that shouldn't be left out!
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of the Dashboard > Merge Requests page) into the CE8-6-stable
and EE8-6-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.6.0-rc3
(be sure to use the correct RC number):-
Merge CE 8-6-stable
into EE8-6-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Tag and build (this is CI-automatized) the 8.6.0-rc3
version using therelease
task:bundle exec rake "release[8.6.0-rc3]"
-
-
Check that packages are built and appears under gitlab/unstable
on https://packages.gitlab.com
18th: (2 working days before the 22nd)
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of the Dashboard > Merge Requests page) into the CE8-6-stable
and EE8-6-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.6.0-rc4
(be sure to use the correct RC number):-
Merge CE 8-6-stable
into EE8-6-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Tag and build (this is CI-automatized) the 8.6.0-rc4
version using therelease
task:bundle exec rake "release[8.6.0-rc4]"
-
-
Check that packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Update GitLab.com with 8.6.0-rc4
-
Tweet about the 8.6.0-rc4
release:GitLab 8.6.0-rc4 is available: https://packages.gitlab.com/gitlab/unstable Use at your own risk. Please link regressions issues from https://gitlab.com/gitlab-org/gitlab-ce/issues/14303
-
Ask in #core
for suggestions about who should be this release's MVP. Once chosen, add them to the blog post and to the MVP page, in the same merge request
21st: (1 working day before the 22nd)
Ideally, the last RC should be released no later than this day and should point to the same commit as the final release.
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of the Dashboard > Merge Requests page) into the CE8-6-stable
and EE8-6-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.6.0-rc5
:-
Merge CE 8-6-stable
into EE8-6-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Tag and build (this is CI-automatized) the 8.6.0-rc5
version using therelease
task:bundle exec rake "release[8.6.0-rc5]"
-
-
Check that packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Update GitLab.com with 8.6.0-rc5
-
Tweet about the 8.6.0-rc5
release:GitLab 8.6.0-rc5 is available: https://packages.gitlab.com/gitlab/unstable Use at your own risk. Please link regressions issues from https://gitlab.com/gitlab-org/gitlab-ce/issues/14303
22nd before 1200 CET:
Release before 1200 CET / 2AM PST, to make sure the majority of our users get the new version on the 22nd and there is sufficient time in the European workday to quickly fix any issues.
-
Merge CE 8-6-stable
into EE8-6-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Try to do before 1100 CET: -
Tag and build (this is CI-automatized) the 8.6.0
version using therelease
task:bundle exec rake "release[8.6.0]"
-
Check that packages are built and appears under gitlab/gitlab-ee
andgitlab/gitlab-ce
on https://packages.gitlab.com
-
-
Try to do before 1200 CET:
-
Update GitLab.com with 8.6.0
-
Create the 8.6.0
version on https://version.gitlab.com -
Publish the release blog post
-
-
Ensure someone tweet about the 8.6.0
release -
Ensure a second tweet of the release announcement is scheduled with the same text at 1800 CET / 8AM PST -
Create the first patch issue using the patch_issue
task:bundle exec rake "patch_issue[8.6.1]"