Release 8.15
1st: (15 working days before the 22nd)
RC1
-
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 -
Have someone run bin/rake gitlab:update_templates
and open a merge request to master with ~"Pick into Stable" -
Merge GitLab CE into EE via merge request: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/960 -
Check for any problematic migrations in EE (EE migrations include CE ones), and paste the diff in a snippet: git diff LATEST_PATCH_TAG-ee..master -- db/migrate
=> https://gitlab.com/snippets/33364 -
Sync CE, EE, and Omnibus to dev
-
In #core
:``` @developers I am about to tag `8.15.0-rc1`. I will still merge `master` into `8-15-stable` until the 16th. ```
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0-rc1
-
Tag the 8.15.0-rc1
version using therelease
task:```sh bundle exec rake "release[8.15.0-rc1]" ```
-
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE & CE -
In #infrastructure
: I'm going to deploy8.15.0-rc1
to staging -
Deploy 8.15.0-rc1
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0-rc1
to production -
Deploy 8.15.0-rc1
to GitLab.com -
Create the regression issue in the CE issue tracker using the regression_issue
task and bookmark it:```sh bundle exec rake "regression_issue[8.15.0]" ```
-
Prepare the blog post using the new_release_post
task, in thewww-gitlab-com
project:```sh bundle exec rake "new_release_post[8.15]" ```
RC2
-
Merge CE master
into CE8-15-stable
-
Merge EE master
into EE8-15-stable-ee
-
Follow the Creating subsequent RCs guide for
8.15.0-rc2
:-
Merge CE 8-15-stable
into EE8-15-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.15.0-rc1-ee..8-15-stable-ee -- db/migrate
=> https://gitlab.com/snippets/33798 -
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0-rc2
-
Tag the 8.15.0-rc2
version using therelease
task:```sh bundle exec rake "release[8.15.0-rc2]" ```
-
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE & CE -
In #infrastructure
: I'm going to deploy8.15.0-rc2
to staging -
Deploy 8.15.0-rc2
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0-rc2
to production -
Deploy 8.15.0-rc2
to GitLab.com -
Tweet about the 8.15.0-rc2
release:``` GitLab 8.15.0-rc2 is available: https://packages.gitlab.com/gitlab/unstable Use at your own risk. Please link regressions issues from LINK_TO_REGRESSION_ISSUE ```
RC3
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.15 merged merge requests page) into the CE8-15-stable
and EE8-15-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.15.0-rc3
(be sure to use the correct RC number):-
Merge CE 8-15-stable
into EE8-15-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.15.0-rc2-ee..8-15-stable-ee -- db/migrate
=> https://gitlab.com/snippets/33917 -
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0-rc3
-
Tag the 8.15.0-rc3
version using therelease
task:```sh bundle exec rake "release[8.15.0-rc3]" ```
-
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE & CE -
In #infrastructure
: I'm going to deploy8.15.0-rc3
to staging -
Deploy 8.15.0-rc3
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0-rc3
to production -
Deploy 8.15.0-rc3
to GitLab.com -
Tweet about the 8.15.0-rc3
release:``` GitLab 8.15.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/25853 ```
RC4
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.15 merged merge requests page) into the CE8-15-stable
and EE8-15-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.15.0-rc4
(be sure to use the correct RC number):-
Merge CE 8-15-stable
into EE8-15-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.15.0-rc3-ee..8-15-stable-ee -- db/migrate
=> https://gitlab.com/snippets/33964 -
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0-rc4
-
Tag the 8.15.0-rc4
version using therelease
task:```sh bundle exec rake "release[8.15.0-rc4]" ```
-
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE & CE -
In #infrastructure
: I'm going to deploy8.15.0-rc4
to staging -
Deploy 8.15.0-rc4
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0-rc4
to production -
Deploy 8.15.0-rc4
to GitLab.com -
Tweet about the 8.15.0-rc4
release:``` GitLab 8.15.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/25853 ```
RC5
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.15 merged merge requests page) into the CE8-15-stable
and EE8-15-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.15.0-rc5
(be sure to use the correct RC number):-
Merge CE 8-15-stable
into EE8-15-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.15.0-rc4-ee..8-15-stable-ee -- db/migrate
=> No migrations included. -
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0-rc5
-
Tag the 8.15.0-rc5
version using therelease
task:```sh bundle exec rake "release[8.15.0-rc5]" ```
-
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE & CE -
In #infrastructure
: I'm going to deploy8.15.0-rc5
to staging -
Deploy 8.15.0-rc5
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0-rc5
to production -
Deploy 8.15.0-rc5
to GitLab.com -
Tweet about the 8.15.0-rc5
release:``` GitLab 8.15.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/25853 ```
RC6
-
Cherry-pick merge requests labeled Picked into Stable
for the current milestone (you can take advantage of thePicked into Stable
8.15 merged merge requests page) into the CE8-15-stable
and EE8-15-stable-ee
branches, respectively -
Follow the Creating subsequent RCs guide for
8.15.0-rc6
(be sure to use the correct RC number):-
Merge CE 8-15-stable
into EE8-15-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.15.0-rc5-ee..8-15-stable-ee -- db/migrate
-
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0-rc6
-
Tag the 8.15.0-rc6
version using therelease
task:```sh bundle exec rake "release[8.15.0-rc6]" ```
-
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE & CE -
In #infrastructure
: I'm going to deploy8.15.0-rc6
to staging -
Deploy 8.15.0-rc6
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0-rc6
to production -
Deploy 8.15.0-rc6
to GitLab.com -
Tweet about the 8.15.0-rc6
release:``` GitLab 8.15.0-rc6 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/25853 ```
13th: (7 working days before the 22nd)
-
Determine QA person and notify this person: MENTION_THIS_PERSON_HERE -
Do QA and fix anything coming out of it: LINK_TO_QA_ISSUE
Anytime between 19th (3 working days before the 22nd) and 21st (1 working day before the 22nd)
-
In #core
:@developers TL;DR: Ensure the `8.15.0` milestone and the `Pick into Stable` label are set, no need to ping me. From now on, please follow the "Change for stable release" process: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#changes-for-stable-releases
19th: (3 working days before the 22nd)
-
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
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.
22nd before 1900 CET:
-
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.15 merged merge requests page) into the CE8-15-stable
and EE8-15-stable-ee
branches, respectively -
Merge CE 8-15-stable
into EE8-15-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.15.0-rc3-ee..8-15-stable-ee -- db/migrate
=> -
Sync CE, EE, and Omnibus to dev
-
Ensure tests are green on CE -
Ensure tests are green on EE -
In #releases
: I'm going to tag8.15.0
-
Tag the 8.15.0
version using therelease
task:```sh bundle exec rake "release[8.15.0]" ```
-
Check that EE packages are built, CE packages are built and appears on packages.gitlab.com
: EE / CE -
Update the version in the VERSION
file to8.16.0-pre
and create thev8.16.0.pre
tag:echo "8.16.0-pre" > VERSION git add VERSION && git ci # ci = commit --gpg-sign --signoff --verbose git pdog # pdog = push dev,origin,github git tag -s v8.16.0.pre -m "Update VERSION to 8.16.0.pre" git pdog v8.16.0.pre:v8.16.0.pre
-
-
Before 0900 PDT / 1800 CET:
-
In #infrastructure
: I'm going to deploy8.15.0
to staging -
Deploy 8.15.0
to staging.gitlab.com -
In #infrastructure
: I'm going to deploy8.15.0
to production -
Deploy 8.15.0
to GitLab.com -
Create the 8.15.0
version on https://version.gitlab.com -
Create the first patch issue using the patch_issue
task:bundle exec rake "patch_issue[8.15.1]"
-
-
At 1000 PDT / 1900 CET:
-
Publish the release blog post -
Ensure someone tweets about the 8.15.0
release
-