@@ -7,12 +7,13 @@ We recommend enterprise customers test the compatibility of new releases with
7
7
their infrastructure on a staging environment before upgrading a production
8
8
deployment.
9
9
10
- We support two release channels:
11
- [ mainline] ( https://github.com/coder/coder/releases/tag/v2.13.0 ) for the bleeding
12
- edge version of Coder and
13
- [ stable] ( https://github.com/coder/coder/releases/latest ) for those with lower
14
- tolerance for fault. We field our mainline releases publicly for one month
15
- before promoting them to stable.
10
+ We support three releases of Coder concurrently. We release
11
+ [ mainline] ( https://github.com/coder/coder/releases/tag/v2.13.0 ) as the bleeding
12
+ edge of Coder with our latest features and
13
+ [ stable] ( https://github.com/coder/coder/releases/latest ) for production
14
+ deployments with a lower tolerance for fault. We field our mainline releases
15
+ publicly for one month before promoting them to stable. The version prior to
16
+ stable receives patches only for security issues or CVEs.
16
17
17
18
### Mainline releases
18
19
@@ -25,10 +26,14 @@ before promoting them to stable.
25
26
26
27
- Safest upgrade/installation path
27
28
- May not include the latest features
28
- - Security vulnerabilities and major bugfixes are supported
29
+ - All bugfixes and security patches are supported
30
+
31
+ ### Security Supported
32
+
33
+ - In-product security vulnerabilities and CVEs are supported
29
34
30
- > Note: We support major security vulnerabilities (CVEs) for the past three
31
- > versions of Coder .
35
+ > For more information on feature rollout, see our
36
+ > [ feature stages documentation ] ( ../contributing/feature-stages.md ) .
32
37
33
38
## Installing stable
34
39
0 commit comments