1
1
#Feature stages
2
2
3
- Some Coder features are released as Alpha or Experimental.
3
+ Some Coder features are released in feature stages before they are generally available.
4
+
5
+ For more information about a specific feature, please contact_ X_ .
4
6
5
7
##Alpha features
6
8
@@ -11,11 +13,33 @@ changelog. In most cases, features will only stay in alpha for 1 month.
11
13
We recommend using[ GitHub issues] ( https://github.com/coder/coder/issues ) to
12
14
leave feedback and get support for alpha features.
13
15
16
+ ##Early access (EA) features
17
+
18
+ Early access features are neither feature-complete nor stable.
19
+ We do not recommend using EA features in production deployments.
20
+
21
+ Coder releases EA features behind an “unsafe” experiment, where they’re
22
+ accessible but not easy to find.
23
+
24
+ ###Early access support expectation
25
+
26
+ Support for early access features is available through_ X_ .
27
+
14
28
##Experimental features
15
29
16
30
These features are disabled by default, and not recommended for use in
17
- production as they may cause performance or stability issues. In most cases,
18
- features will only stay in experimental for 1-2 weeks of internal testing.
31
+ production as they may cause performance or stability issues.
32
+ In most cases, experimental features are complete, but require further
33
+ internal testing and will only stay in the experimental stage for one or
34
+ two weeks.
35
+
36
+ Coder may make significant changes to experiments or revert features to a
37
+ feature flag at any time.
38
+
39
+ If you plan to activate an experimental feature, we suggest that you use
40
+ a staging deployment.
41
+
42
+ You can opt-out of an experiment after you've enabled it.
19
43
20
44
``` yaml
21
45
# Enable all experimental features
@@ -27,7 +51,11 @@ coder server --experiments=feature1,feature2
27
51
# Alternatively, use the `CODER_EXPERIMENTS` environment variable.
28
52
```
29
53
30
- ##Available experimental features
54
+ ###Experimental features support expectation
55
+
56
+ Support for experimental features is available through_ X_ .
57
+
58
+ ###Available experimental features
31
59
32
60
<!-- Code generated by scripts/release/docs_update_experiments.sh. DO NOT EDIT.-->
33
61
<!-- BEGIN: available-experimental-features-->
@@ -37,3 +65,13 @@ coder server --experiments=feature1,feature2
37
65
| ` notifications ` | Sends notifications via SMTP and webhooks following certain events.| mainline, stable|
38
66
39
67
<!-- END: available-experimental-features-->
68
+
69
+ ##Beta
70
+
71
+ Beta features are open to the public, but are tagged with a` Beta ` label.
72
+
73
+ They’re subject to minor changes and may contain bugs, but are generally ready for use.
74
+
75
+ ###Beta features support expectation
76
+
77
+ Support for beta features is available through_ X_ .