You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/policy/experiment-beta-support.md
+33-12Lines changed: 33 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ description: Support details.
5
5
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://handbook.gitlab.com/handbook/product/ux/technical-writing/#assignments
6
6
---
7
7
8
-
# Support for experiment, beta, and generally available features
8
+
# Support for experiment, beta, and publicly available features
9
9
10
10
GitLab sometimes releases features as experimental or beta, and users can opt in and test the new experience.
11
11
Some reasons for these kinds of feature releases include:
@@ -14,10 +14,10 @@ Some reasons for these kinds of feature releases include:
14
14
- Features not complete enough to be considered an [MVC](https://handbook.gitlab.com/handbook/product/product-principles/#the-minimal-valuable-change-mvc),
15
15
but added to the codebase as part of the development process.
16
16
17
-
Please note that some features may not be aligned to these recommendations if they were developed before the recommendations were in place,
17
+
Some features may not be aligned to these recommendations if they were developed before the recommendations were in place,
18
18
or if a team determined an alternative implementation approach was needed.
19
19
20
-
All other features are considered to be generally available (GA).
20
+
All other features are considered to be publicly available.
21
21
22
22
## Experiment
23
23
@@ -47,18 +47,37 @@ Beta features:
47
47
- Have a user experience that is complete or near completion.
48
48
- Can be equivalent to partner "Public Preview" status.
49
49
50
-
## Generally available (GA)
50
+
## Public availability
51
+
52
+
Two types of public releases are available:
53
+
54
+
- Limited availability (LA)
55
+
- Generally available (GA)
56
+
57
+
Both types are production-ready, but have different scopes.
58
+
59
+
### Limited availability (LA)
60
+
61
+
Limited availability features:
62
+
63
+
- Are ready for production use at a reduced scale.
64
+
- Might initially be free, then become paid when generally available.
65
+
- Might be offered at a discount before becoming generally available.
66
+
- Might have commercial terms that change for new contracts when generally available.
67
+
- Are [fully supported](https://about.gitlab.com/support/statement-of-support/) and documented.
68
+
- Have a complete user experience aligned with GitLab design standards.
69
+
70
+
### Generally available (GA)
51
71
52
72
Generally available features:
53
73
54
74
- Are ready for production use at any scale.
55
75
- Are [fully supported](https://about.gitlab.com/support/statement-of-support/) and documented.
56
76
- Have a complete user experience aligned with GitLab design standards.
57
77
58
-
## All features are in production
78
+
## Production features
59
79
60
-
All experimental, beta, and generally available features are available on GitLab.com,
61
-
so they are all considered to be "in production".
80
+
All experimental, beta, and publicly available features are available on GitLab.com and are considered in production.
62
81
63
82
## GitLab experiment and beta development guidelines
64
83
@@ -76,7 +95,7 @@ could create significant risks or friction for GitLab users or the platform, suc
76
95
In addition to the [experiment details](#experiment) for users, experiments should:
77
96
78
97
- Offer a way to opt in with minimal friction. For example, needing to flip a feature flag is too much friction,
79
-
but a group or project-level setting in the UI is not.
98
+
but a group or project setting in the UI is not.
80
99
- Link out to the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/) in the opt-in.
81
100
- Have documentation that reflects that the feature is subject to the [GitLab Testing Agreement](https://handbook.gitlab.com/handbook/legal/testing-agreement/).
82
101
- Have [UI that reflects the experiment status](https://design.gitlab.com/usability/feature-management#highlighting-feature-versions).
@@ -107,11 +126,13 @@ All beta features that [meet the review criteria](https://handbook.gitlab.com/ha
107
126
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)
108
127
by following the [Production Readiness Review process](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/readiness/#process).
109
128
110
-
### GA features
129
+
### Publicly available features
130
+
131
+
Publicly available features must:
111
132
112
-
Generally available features that [meet the review criteria](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/readiness/#criteria-for-starting-a-production-readiness-review)
113
-
must complete the [Production Readiness Review](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/readiness/)
114
-
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).
133
+
1. Meet the [review criteria](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/readiness/#criteria-for-starting-a-production-readiness-review).
134
+
1. Complete the [Production Readiness Review](https://handbook.gitlab.com/handbook/engineering/infrastructure/production/readiness/).
135
+
1. 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).
0 commit comments