GitLab release and maintenance policy

The Delivery Group are the owners of the maintenance policy and must approve any requested updates. This follows our DRI model and is in place to ensure predictability for customers.

GitLab has strict policies governing version naming, as well as release pace for major, minor, patch releases. New releases are announced on the GitLab blog.

Our current policy is:

  • Backporting bug fixes for only the current stable release at any given time - see patch releases below.
  • Backporting security fixes to the previous two monthly releases in addition to the current stable release. In some circumstances (outlined in patch releases below) we may address a security vulnerability to the current stable release only or in the regular monthly release process, with no backports.

In rare cases, release managers may make an exception and backport to more than the last two monthly releases. See Backporting to older releases for more information.

Versioning

GitLab uses Semantic Versioning for its releases: (Major).(Minor).(Patch).

For example, for GitLab version 13.10.6:

  • 13 represents the major version. The major release was 13.0.0 but often referred to as 13.0.
  • 10 represents the minor version. The minor release was 13.10.0 but often referred to as 13.10.
  • 6 represents the patch number.

Any part of the version number can increment into multiple digits, for example, 13.10.11.

The following table describes the version types and their release cadence:

Version type Description Cadence
Major For significant changes, or when any backward-incompatible changes are introduced to the public API. Yearly. The next major release is GitLab 18.0, scheduled for May 15th, 2025. GitLab schedules major releases for May each year, by default.
Minor For when new backward-compatible functionality is introduced to the public API, a minor feature is introduced, or when a set of smaller features is rolled out. Monthly, scheduled for the third Thursday of each month.
Patch For backward-compatible bug fixes that fix incorrect behavior. See Patch releases. Bi-monthly, scheduled for the Wednesday the week before and the Wednesday the week after the monthly minor release.

Upgrade recommendations

We encourage everyone to run the latest stable release to ensure that you can upgrade to the most secure and feature-rich GitLab experience. To make sure you can run the most recent stable release, we are working hard to keep the update process reliable.

If you are unable to follow our monthly release cycle, there are a couple of cases you must consider. Follow the upgrade paths guide to safely upgrade between versions.

Version-specific change documentation for Linux packages is available for:

Instructions are available for downloading the Linux package locally and manually installing it.

A step-by-step guide to upgrading the Linux package-bundled PostgreSQL is documented separately.

Upgrading major versions

Backward-incompatible changes and migrations are reserved for major versions. For more information, see Create a GitLab upgrade plan.

Patch releases

Patch releases include bug fixes for the current stable released version of GitLab and security fixes to the previous two monthly releases in addition to the current stable release.

These policies are in place because:

  1. GitLab has Community and Enterprise distributions, doubling the amount of work necessary to test/release the software.
  2. Backporting to older releases creates a high development, quality assurance, and support cost.
  3. Supporting parallel version discourages incremental upgrades which over time accumulate in complexity and create upgrade challenges for all users. GitLab has a dedicated team ensuring that incremental upgrades (and installations) are as simple as possible.
  4. The number of changes created in the GitLab application is high, which contributes to backporting complexity to older releases. In several cases, backporting has to go through the same review process a new change goes through.
  5. Ensuring that tests pass on the older release is a considerable challenge in some cases, and as such is very time-consuming.

Including new features in a patch release is not possible as that would break Semantic Versioning. Breaking Semantic Versioning has the following consequences for users that have to adhere to various internal requirements (for example, org. compliance, verifying new features, and similar):

  1. Inability to quickly upgrade to leverage bug fixes included in patch versions.
  2. Inability to quickly upgrade to leverage security fixes included in patch versions.
  3. Requirements consisting of extensive testing for not only stable GitLab release, but every patch version.

For highly severe security issues, there is precedent to backport security fixes to even more previous GitLab release versions. This decision is made on a case-by-case basis.

In some circumstances, we may choose to address a vulnerability using the regular monthly release process by updating the active and current stable releases only, with no backports. Factors influencing this decision include the very low likelihood of exploitation, the low impact of the vulnerability, the complexity of security fixes and the eventual risk to stability. We always address high and critical security issues with a patch release.

In cases where a strategic user has a requirement to test a feature before it is officially released, we can offer to create a Release Candidate (RC) version that includes the specific feature. This should be needed only in extreme cases and can be requested for consideration by raising an issue in the release/tasks issue tracker. It is important to note that the Release Candidate contains other features and changes as it is not possible to easily isolate a specific feature (similar reasons as noted above). The Release Candidate is no different than any code that is deployed to GitLab.com or is publicly accessible.

Backporting to older releases

Backporting to more than one stable release is usually reserved for security fixes. In some cases, however, we may need to backport a bug fix to more than one stable release, depending on the severity of the bug.

The decision on whether backporting a change is performed is done at the discretion of the current release managers, based on all of the following:

  1. Estimated severity of the bug: Highest possible impact to users based on the current definition of severity.
  2. Estimated priority of the bug: Immediate impact on all impacted users based on the above estimated severity.
  3. Potentially incurring data loss and/or security breach.
  4. Potentially affecting one or more strategic accounts due to a proven inability by the user to upgrade to the current stable version.

If all of the above are satisfied, the backport releases can be created for the current stable release, and two previous monthly releases. In rare cases a release manager may grant an exception to backport to more than two previous monthly releases. For instance, if we release 13.2.1 with a fix for a severe bug introduced in 13.0.0, we could backport the fix to a new 13.0.x, and 13.1.x patch release.

Note that severity 3 and lower requests are automatically turned down.

To request backporting to more than one stable release for consideration, raise an issue in the release/tasks issue tracker.

More information

You may also want to read our: