Skip to content
Snippets Groups Projects
New issue look: Off

Release 8.8

    • Closed Issue created by yorickpeterse-staging @yorickpeterse

    29th: (16 working days before the 22nd)

    2nd: (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

      • Create the Update guides

      • Merge GitLab CE into EE via merge request: LINK_TO_CE_EE_MR

      • In #operations (be sure to mention people than can deploy to GitLab.com):

        I am starting the release tasks for `8.8.0-rc1` (LINK_TO_THIS_ISSUE).
Will anyone be available to deploy it to GitLab.com when the packages are built?

      • In #development:

        I am about to tag `8.8.0-rc1`. I will still merge `master` into `8-8-stable` until the 17th. 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.8.0!

        or if the RC has already been tagged and people should follow the Pick into Stable workflow:

        TL;DR: Ensure the `8.8.0` milestone and the `Pick into Stable` label are set, no need to ping me.

`8.8.0-rc1` was tagged (rc1 was tagged before the Git vulnerability “fix”) 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.8.0`!

      • Ensure tests are green on CE: https://gitlab.com/gitlab-org/gitlab-ce/commits/8-8-stable

      • Ensure tests are green on EE: https://gitlab.com/gitlab-org/gitlab-ee/commits/8-8-stable-ee

      • Tag and build (this is CI-automatized) the 8.8.0-rc1 version using the release task:

        bundle exec rake "release[8.8.0-rc1]"

    • Create the regression issue in the CE issue tracker using the regression_issue task and bookmark it:

      bundle exec rake "regression_issue[8.8.0]"

    • Check that packages are built and appears under gitlab/unstable on https://packages.gitlab.com

    • Check for any migrations in CE (and paste the diff below): git diff LATEST_PATCH_TAG..8-8-stable -- db/

    • Check for any migrations in EE (and paste the diff below): git diff LATEST_PATCH_TAG-ee..8-8-stable-ee -- db/

    • Deploy 8.8.0-rc1 to GitLab.com

    • Prepare the blog post using the new_release_post task, in the www-gitlab-com project:

      bundle exec rake "new_release_post[8.8]"

    Anytime beetween 2nd (15 working days before the 22nd) and 17th (4 working days before the 22nd)

    Copy-paste the tasks below for any other RCs (be sure to update the RC number).

    Only after the 12th (7 working days before the 22nd)

    • Tweet about the 8.8.0-rc2 release:

      GitLab 8.8.0-rc2 is available: https://packages.gitlab.com/gitlab/unstable
Use at your own risk. Please link regressions issues from
LINK_TO_REGRESSION_ISSUE

    12th: (7 working days before the 22nd)

    Anytime beetween 18th (3 working days before the 22nd) and 20th (1 working day before the 22nd)

    Copy-paste the tasks below for any other RCs (be sure to update the RC number).

    18th: (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!

    19th: (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

    20th: (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 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.

    47 of 53 checklist items completed

    Designs

      Child items ...

      2. Activity

      Please register or sign in to reply