diff options
Diffstat (limited to 'doc/policy')
-rw-r--r-- | doc/policy/alpha-beta-support.md | 11 | ||||
-rw-r--r-- | doc/policy/experiment-beta-support.md | 12 | ||||
-rw-r--r-- | doc/policy/maintenance.md | 4 |
3 files changed, 12 insertions, 15 deletions
diff --git a/doc/policy/alpha-beta-support.md b/doc/policy/alpha-beta-support.md deleted file mode 100644 index bfea5b3a2d6..00000000000 --- a/doc/policy/alpha-beta-support.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -redirect_to: 'experiment-beta-support.md' -remove_date: '2023-09-07' ---- - -This document was moved to [another location](experiment-beta-support.md). - -<!-- This redirect file can be deleted after <2023-09-07>. --> -<!-- Redirects that point to other docs in the same project expire in three months. --> -<!-- Redirects that point to docs in a different project or site (for example, link is not relative and starts with `https:`) expire in one year. --> -<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html --> diff --git a/doc/policy/experiment-beta-support.md b/doc/policy/experiment-beta-support.md index 68cc96f118b..a87a72d7910 100644 --- a/doc/policy/experiment-beta-support.md +++ b/doc/policy/experiment-beta-support.md @@ -13,6 +13,9 @@ All other features are considered to be Generally Available (GA). ## Experiment Support is not provided for features listed as "Experimental" or "Alpha" or any similar designation. Issues regarding such features should be opened in the GitLab issue tracker. Teams should release features as GA from the start unless there are strong reasons to release them as Experiment or Beta versions first. +All Experimental features must [initiate Production Readiness Review](https://about.gitlab.com/handbook/engineering/infrastructure/production/readiness/#process) and complete the [experiment section in the readiness template](https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md#experiment). + +Experimental features are: - Not ready for production use. - No support available. @@ -20,7 +23,7 @@ Support is not provided for features listed as "Experimental" or "Alpha" or any - Can be removed at any time. - Data loss may occur. - Documentation may not exist or just be in a blog format. -- Offer an easy way to choose to opt-in to experimental features with minimal friction. For example, needing to flip a feature flag is too much friction, but a group or project-level setting that is in the UI is not. +- Offer a way to opt-in with minimal friction. For example, needing to flip a feature flag is too much friction, but a group or project-level setting in the UI is not. - Link out to the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/) in the opt-in. - Documentation reflects that the feature is subject to the [GitLab Testing Agreement](https://about.gitlab.com/handbook/legal/testing-agreement/). - [UI reflects experiment status](https://design.gitlab.com/usability/feature-management#highlighting-feature-versions). @@ -33,6 +36,9 @@ Support is not provided for features listed as "Experimental" or "Alpha" or any ## Beta Commercially-reasonable efforts are made to provide limited support for features designated as "Beta," with the expectation that issues require extra time and assistance from development to troubleshoot. +All Beta features must complete all sections up to and including the [beta section in the readiness template](https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md#beta) by following the [Production Readiness Review process](https://about.gitlab.com/handbook/engineering/infrastructure/production/readiness/#process). + +Beta features are: - May not be ready for production use. - Support on a commercially-reasonable effort basis. @@ -50,7 +56,9 @@ Commercially-reasonable efforts are made to provide limited support for features ## Generally Available (GA) -Generally Available features means that they passed the [Production Readiness Review](https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md) for GitLab.com, and are: +Generally Available features must complete the [Production Readiness Review](https://about.gitlab.com/handbook/engineering/infrastructure/production/readiness) and complete all sections up to and including the [GA section in the readiness template](https://gitlab.com/gitlab-com/gl-infra/readiness/-/blob/master/.gitlab/issue_templates/production_readiness.md#general-availability). + +GA features are: - Ready for production use at any scale. - Fully documented and supported. diff --git a/doc/policy/maintenance.md b/doc/policy/maintenance.md index a6de6f594fb..bb27fcb27e0 100644 --- a/doc/policy/maintenance.md +++ b/doc/policy/maintenance.md @@ -36,8 +36,8 @@ 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 16.0 on May 22, 2023. GitLab schedules major releases on May 22 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 on the 22nd. | +| Major | For significant changes, or when any backward-incompatible changes are introduced to the public API. | Yearly. The next major release is GitLab 17.0, scheduled for May 16th, 2024. GitLab [schedules major releases](https://about.gitlab.com/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. | | Patch | For backward-compatible bug fixes that fix incorrect behavior. See [Patch releases](#patch-releases). | As needed. | ## Upgrade recommendations |