Major Releases Working Group

Attributes

Closing update

This group is closed with the outcome of the group consolidating in and opinion on breaking changes that the org can adopt:

• Migrations over breaking things 2024 Executive Brief (internal)
• Migrations over breaking things 2024 SLides (internal)
• Migrations over breaking things 2024 Recording (internal)

Purpose

The `Major Releases Working Group aims to minimise any negative customer impact related to the major release and breaking change across SaaS and self manged GitLab users.

Overview

The Major release working group will form from the point that all deprecations have been announced that are due for the major release according to the deprecation policy until we are at least one milestone past the major release and aware of any customer issues that have arisen as part of the major upgrade and have a plan of action. The rough schedule for this is outlined in the attributes table above.

Goals

This is a non-comprehensive list of topics to be discussed.

• Minimise customer impact due to breaking change and major release.
• Go through product deprecations and separate the high impact ones for further analysis.
• Prepare Support and CS for customer questions on deprecations & upgrade - Internal Slides.
• Release communications to prepare customers.
• Understand whether deprecation policy and GitLab’s working interpretation are aligned / need to be changed.
• Put a plan in place to improve conditions for next major release and remove need for this working group next iteration.

Exit Criteria

Exit Criteria are avaialable in the Future Major Release Coordination & Improvements Epic.

Roles and Responsibilities

View page source - Edit this page - please contribute.