Release 8.10
30th: (16 working days before the 22nd)
-
Triage the Omnibus milestone
1st: (15 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: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5097 -
Create the Update guides: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/524 & gitlab-org/gitlab-ee!534 -
Have someone run bin/rake gitlab:update_templates
and open a merge request tomaster
: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5107 -
Merge GitLab CE into EE via merge request: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/528 -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.9.5-ee..master -- db/
=> https://gitlab.com/gitlab-org/gitlab-ce/snippets/22115 -
In #infrastructure
(be sure to mention people than can deploy to GitLab.com):``` I am starting the release tasks for `8.10.0-rc1` (https://gitlab.com/gitlab-org/gitlab-ce/issues/19391). Will anyone be available to help me if anything goes wrong when deploying to GitLab.com? ```
-
In #development
:``` I am about to tag `8.10.0-rc1`. I will still merge `master` into `8-10-stable` until the 18th. After that, please follow the "Change for stable release" process: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#changes-for-stable-releases (TL;DR: Ensure the milestone and the `Pick into Stable` label are set, no need to ping me.) Looking forward to merging/picking all your cool stuff in 8.10.0! ``` or if the RC has already been tagged and people should follow the `Pick into Stable` workflow: ``` TL;DR: Ensure the `8.10.0` milestone and the `Pick into Stable` label are set, no need to ping me. `8.10.0-rc1` was tagged and deployed today. Please 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.10.0`! ```
-
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/master -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/master -
Tag and build (this is CI-automated) the 8.10.0-rc1
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc1]" ```
-
-
Create the regression issue in the CE issue tracker using the regression_issue
task and bookmark it:```sh bundle exec rake "regression_issue[8.10.0]" ```
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
DeployAborted due to migration timeout8.10.0-rc1
to staging.gitlab.com -
Deploy8.10.0-rc1
to GitLab.com -
Prepare the blog post using the new_release_post
task, in thewww-gitlab-com
project:```sh bundle exec rake "new_release_post[8.10]" ``` https://gitlab.com/gitlab-com/www-gitlab-com/merge_requests/2497
Anytime between 1st (15 working days before the 22nd) and 18th (4 working days before the 22nd)
Copy-paste the tasks below for any other RCs (be sure to update the RC number).
7th (Thursday): RC2
-
Merge CE master
into CE8-10-stable
- Follow the Creating subsequent RCs guide for
8.10.0-rc2
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Ensure tests are green on CE: https://gitlab.com/gitlab-org/gitlab-ce/commits/8-10-stable -
Ensure tests are green on EE: https://gitlab.com/gitlab-org/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc2
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc2]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
DeployAborted due to migration timeout8.10.0-rc2
to staging.gitlab.com
8th (Friday): RC3
-
Merge CE master
into CE8-10-stable
- Follow the Creating subsequent RCs guide for
8.10.0-rc3
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc3
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc3]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Check for any migrations in EE (and paste the diff below): git diff v8.10.0-rc2-ee..8-10-stable-ee -- db/
-
DeployAborted due to migration timeout8.10.0-rc3
to staging.gitlab.com -
Deploy8.10.0-rc3
to GitLab.com
11th (Monday): RC4
-
Merge CE master
into CE8-10-stable
- Follow the Creating subsequent RCs guide for
8.10.0-rc4
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.9.6-ee..8-10-stable-ee -- db/
-
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc4
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc4]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy 8.10.0-rc4
to staging.gitlab.com -
Deploy8.10.0-rc4
to GitLab.com
13th: (7 working days before the 22nd)
-
Merge CE master
into CE8-10-stable
-
Merge EE master
into EE8-10-stable-ee
- Follow the Creating subsequent RCs guide for
8.10.0-rc5
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet:git diff v8.9.6-ee..8-10-stable-ee -- db/
-
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc5
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc5]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy8.10.0-rc5
to staging.gitlab.com -
Deploy8.10.0-rc5
to GitLab.com -
Determine QA person and notify this person: @kelvinmutuma -
Do QA and fix anything coming out of it: https://gitlab.com/gitlab-org/gitlab-ce/issues/20030
15th (5 working days before the 22nd): RC6, RC7
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively - Follow the Creating subsequent RCs guide for
8.10.0-rc6
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Ensure tests are green on CE: https://gitlab.com/gitlab-org/gitlab-ce/commits/8-10-stable -
Ensure tests are green on EE: https://gitlab.com/gitlab-org/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc6
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc6]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc5-ee..8-10-stable-ee -- db/
-
Deploy 8.10.0-rc6
to staging.gitlab.com -
Deploy8.10.0-rc6
to GitLab.com
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.10.0-rc7
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Ensure tests are green on CE: https://gitlab.com/gitlab-org/gitlab-ce/commits/8-10-stable -
Ensure tests are green on EE: https://gitlab.com/gitlab-org/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc7
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc7]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc5-ee..8-10-stable-ee -- db/
-
Deploy 8.10.0-rc7
to staging.gitlab.com -
Deploy 8.10.0-rc7
to GitLab.com -
Tweet about the 8.10.0-rc7
release:``` GitLab 8.10.0-rc7 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/19582 ```
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.10.0-rc8
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Ensure tests are green on CE: https://gitlab.com/gitlab-org/gitlab-ce/commits/8-10-stable -
Ensure tests are green on EE: https://gitlab.com/gitlab-org/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc8
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc8]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc7-ee..8-10-stable-ee -- db/
-
Deploy 8.10.0-rc8
to staging.gitlab.com -
Deploy 8.10.0-rc8
to GitLab.com -
Tweet about the 8.10.0-rc8
release:``` GitLab 8.10.0-rc8 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/19582 ```
18th: (4 working days before the 22nd)
RC9
-
Merge CE master
into CE8-10-stable
-
Merge EEmaster
into EE8-10-stable-ee
- Follow the Creating subsequent RCs guide for
8.10.0-rc9
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc8-ee..8-10-stable-ee -- db/
https://gitlab.com/gitlab-org/gitlab-ce/snippets/22652 -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc9
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc9]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
DeployA migration wouldn't run with a transaction open.8.10.0-rc9
to staging.gitlab.com
RC10
-
Merge CE master
into CE8-10-stable
-
Merge EEmaster
into EE8-10-stable-ee
-
Follow the Creating subsequent RCs guide for
8.10.0-rc10
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc8-ee..8-10-stable-ee -- db/
https://gitlab.com/gitlab-org/gitlab-ce/snippets/22652 -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc10
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc10]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy 8.10.0-rc10
to staging.gitlab.com -
Deploy 8.10.0-rc10
to GitLab.com -
Tweet about the 8.10.0-rc10
release:``` GitLab 8.10.0-rc10 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/19582 ```
Anytime between 19th (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 thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.10.0-rc3
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc2-ee..8-10-stable-ee -- db/migrate
-
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc3
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc3]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy 8.10.0-rc3
to staging.gitlab.com -
Deploy 8.10.0-rc3
to GitLab.com -
Tweet about the 8.10.0-rc3
release:``` GitLab 8.10.0-rc3 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/19582 ```
19th: (3 working days before the 22nd)
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.10.0-rc11
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc10-ee..8-10-stable-ee -- db/migrate
=> https://gitlab.com/gitlab-org/gitlab-ce/snippets/22736 -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc11
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc11]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy 8.10.0-rc11
to staging.gitlab.com -
Deploy 8.10.0-rc11
to GitLab.com -
Tweet about the 8.10.0-rc11
release:``` GitLab 8.10.0-rc11 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/19582 ```
-
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! ```
20th: (2 working days before the 22nd)
-
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
RC12
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.10.0-rc12
:-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc11-ee..8-10-stable-ee -- db/migrate
=> https://gitlab.com/gitlab-org/gitlab-ce/snippets/22843 -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc12
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc12]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy 8.10.0-rc12
to staging.gitlab.com -
Deploy 8.10.0-rc12
to GitLab.com -
Tweet about the 8.10.0-rc12
release:``` GitLab 8.10.0-rc12 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/19582 ```
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.
RC13
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively - Follow the Creating subsequent RCs guide for
8.10.0-rc13
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc12-ee..8-10-stable-ee -- db/migrate
=> https://gitlab.com/gitlab-org/gitlab-ce/snippets/22886 -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Tag and build (this is CI-automated) the 8.10.0-rc13
version using therelease
task:```sh bundle exec rake "release[8.10.0-rc13]" ```
-
-
Check that EE packages are built and CE packages are built and appears under gitlab/unstable
on https://packages.gitlab.com -
Deploy 8.10.0-rc13
to staging.gitlab.com -
Deploy 8.10.0-rc13
to GitLab.com
RC14
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively - Follow the Creating subsequent RCs guide for
8.10.0-rc14
(be sure to use the correct RC number):-
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Sync CE, EE, and Omnibus to dev
-
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc12-ee..8-10-stable-ee -- db/migrate
=> -
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee
-
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.
-
Before 0800 PDT / 1700 CET:
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.10 merged merge requests page) into the CE8-10-stable
and EE8-10-stable-ee
branches, respectively -
Merge CE 8-10-stable
into EE8-10-stable-ee
following the Merging a CE stable branch into its EE counterpart guide -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff v8.10.0-rc13-ee..8-10-stable-ee -- db/migrate
=> -
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE: https://dev.gitlab.org/gitlab/gitlabhq/commits/8-10-stable -
Ensure tests are green on EE: https://dev.gitlab.org/gitlab/gitlab-ee/commits/8-10-stable-ee -
Communicate the following action in #releases
-
Tag the 8.10.0
version using therelease
task:```sh bundle exec rake "release[8.10.0]" ```
-
Check that EE packages are built, and CE packages are built
-
-
Update the version in the VERSION
file to8.11.0-pre
and create thev8.11.0.pre
tag:echo "8.11.0-pre" > VERSION git add VERSION && git ci # ci = commit --gpg-sign --signoff --verbose git tag -s v8.11.0.pre -m "Update VERSION to 8.11.0.pre" git pdog # pdog = push dev,origin,github git pdog v8.11.0.pre:v8.11.0.pre
-
Before 0900 PDT / 1800 CET:
-
Communicate the following actions in #infrastructure
-
Deploy 8.10.0
to staging.gitlab.com -
Deploy 8.10.0
to GitLab.com -
Check that the 8.10.0
version was automatically created on https://version.gitlab.com -
Create the first patch issue using the patch_issue
task:bundle exec rake "patch_issue[8.10.1]"
-
-
At 1000 PDT / 1900 CET:
-
Publish the release blog post -
Ensure someone tweets about the 8.10.0
release -
Upgrade the #gitlab
channel's topic on IRC Freenode with the latest version number
-