Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab FOSS
GitLab FOSS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Issues
  • #13167

Closed
Open
Opened Feb 03, 2016 by Rémy Coutable@rymai⛰Maintainer40 of 41 tasks completed40/41 tasks

Release 8.5

9th: (9 working days before the 22nd)

  • Triage the Omnibus milestone
  • Determine QA person and notify this person: @kelvinmutuma

11th: (7 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 (CE: !2766 (merged), EE: gitlab-org/gitlab-ee!171)

    • Create the Update guides (CE: !2766 (merged), EE: gitlab-org/gitlab-ee!171)

    • Merge CE master into EE master: gitlab-org/gitlab-ee!175

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

      We’re starting the release tasks for `8.5.0-rc1`. Will anyone be able/available to
      deploy when the packages are out?
    • In #development:

      @here: We're about to release `8.5.0-rc1`. We will still merge
      `master` into `8-5-stable` for a few days (ideally no
      later than the 16th), but after that we will switch to the
      picking strategy documented here:
      https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#changes-for-stable-releases
      
      Please become familiar with this “process". Thanks in advance!
      
      Looking forward to merging/picking all your cool stuff in <%= version.to_patch %>!
    • Tag and build the 8.5.0-rc1 version using the release tools. (will auto-release the packages)

  • Update GitLab.com with 8.5.0-rc1

  • Create the regression issue in the CE issue tracker: #13350 (closed)

  • Tweet about 8.5.0-rc1 release:

    GitLab 8.5.0-rc1 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/13350
  • Do QA and fix anything coming out of it: #13380 (closed).

  • Close the Omnibus milestone

17th: (3 working days before the 22nd)

  • Merge ce/master into ce/8-5-stable

  • Cherry-pick EE merge requests labeled Picked into Stable

  • Create new 8.5.0-rc2, following the Creating subsequent RCs guide:

    • Merge ce/8-5-stable into ee/8-5-stable-ee following the Merging a CE stable branch into its EE counterpart guide
    • Tag and build the 8.5.0-rc2 version using the release tools. (will auto-release the packages)
  • Update GitLab.com with 8.5.0-rc2

  • Tweet about 8.5.0-rc2 release:

    GitLab 8.5.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/13350
  • Prepare the blog post

18th: (2 working days before the 22nd)

  • Check that MVP is added to the MVP page

  • Cherry-pick CE merge requests labeled Picked into Stable

  • Cherry-pick EE merge requests labeled Picked into Stable

  • 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: (1 working day before the 22nd)

  • Cherry-pick CE merge requests labeled Picked into Stable

  • Cherry-pick EE merge requests labeled Picked into Stable

  • Create new 8.5.0-rc3, following the Creating subsequent RCs guide:

    • Merge ce/8-5-stable into ee/8-5-stable-ee following the Merging a CE stable branch into its EE counterpart guide
    • Tag and build the 8.5.0-rc3 version using the release tools. (will auto-release the packages)
  • Update GitLab.com with 8.5.0-rc3

  • Tweet about 8.5.0-rc3 release:

    GitLab 8.5.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/13350

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.

  • Remove (unreleased) from CHANGELOG
  • Remove (unreleased) from CHANGELOG-EE (in gitlab-ee)
  • Merge 8-5-stable into 8-5-stable-ee following the Merging a CE stable branch into its EE counterpart guide
  • Create the '8.5.0' tag with the release tools
  • Try to do before 1100 CET: Tag and build the 8.5.0 version using the release tools (will auto-release the packages)
  • Try to do before 1200 CET: Update GitLab.com with 8.5.0
  • Try to do before 1200 CET: Publish the release blog post
  • Create the 8.5.0 version on version.gitlab.com
  • Tweet about the release
  • Schedule a second Tweet of the release announcement with the same text at 1800 CET / 8AM PST
Assignee
Assign to
8.5
Milestone
8.5 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab-foss#13167