@@ -7,10 +7,13 @@ We recommend enterprise customers test the compatibility of new releases with
77their infrastructure on a staging environment before upgrading a production
88deployment.
99
10- We support two release channels:[ mainline] ( #mainline-releases ) for the bleeding
11- edge version of Coder and[ stable] ( #stable-releases ) for those with lower
10+ We support two release channels:
11+ [ mainline] ( https://github.com/coder/coder/releases/tag/v2.16.0 ) for the bleeding
12+ edge version of Coder and
13+ [ stable] ( https://github.com/coder/coder/releases/latest ) for those with lower
1214tolerance for fault. We field our mainline releases publicly for one month
13- before promoting them to stable.
15+ before promoting them to stable. The version prior to stable receives patches
16+ only for security issues or CVEs.
1417
1518###Mainline releases
1619
@@ -23,10 +26,14 @@ before promoting them to stable.
2326
2427- Safest upgrade/installation path
2528- May not include the latest features
26- - Security vulnerabilities and major bugfixes are supported
29+ - All bugfixes and security patches are supported
30+
31+ ###Security Support
32+
33+ - In-product security vulnerabilities and CVEs are supported
2734
28- > Note: We support major security vulnerabilities (CVEs) for the past three
29- > versions of Coder .
35+ > For more information on feature rollout, see our
36+ > [ feature stages documentation ] ( ../contributing/feature-stages.md ) .
3037
3138##Installing stable
3239