Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Product Milestones

  1. You are here:
  2. Handbook
  3. Product Handbook
  4. Product Milestones

When planning, Product Managers plan to GitLab milestones. Here is the process for creating and maintaining them.

Product Milestone Creation

One quarter ahead, the Product Operations team will create all of the necessary milestones for the next quarter. Our standard practice is to have the Major release every May, resulting in:

XX.0 - May 22
XX.1 - June 22
XX.2 - July 22
XX.3 - August 22
XX.4 - September 22
XX.5 - October 22
XX.6 - November 22
XX.7 - December 22
XX.8 - January 22
XX.9 - February 22
XX.10 - March 22
XX.11 - April 22

To update the milestones in GitLab, Product Operations follows these steps:

Step 1: .org

  1. Ensure that the relevant milestones are created. Go to GitLab Milestones for .org
  2. Click on New milestone in the top right
  3. Title the milestone with the dot release that makes sense.
    • Note: We iterate through the .0 and further for each release with the .0 release every May.
  4. Set end date to the appropriate month with the 18th to the 17th
  5. Closing milestones happens in the Engineering workflow

Step 2: .com

  1. Ensure that .com mirrors the .org milestones for consistency in Product, Marketing etc.
  2. Ensure that the relevant milestones are created. Go to GitLab Milestones for .com
  3. Click on New milestone in the top right
  4. Title the milestone with the dot release that matches .org.
    • Note: We iterate through the .0 and further for each release with the .0 release every May.
  5. Set end date to the appropriate month with the 18th to the 17th
  6. Closing milestones happens in the Engineering workflow

Understanding Releases

The release definitions are maintained by the Engineering Team and we run the end of each Milestone on the 22nd.

Product Milestones Usage

Open in Web IDE View source