- Notifications
You must be signed in to change notification settings - Fork928
docs: document new feature stages#16719
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes from1 commit
098ada04ec822fb6d5cfd28ea285734a0d291743bba4d0b91a8ca4046e82c46fd85a79File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -9,37 +9,37 @@ If you encounter an issue with any Coder feature, please submit a | ||||||
| ## Early access features | ||||||
| - **Stable**: No | ||||||
| - **Production-ready**: No | ||||||
| - **Support**: GitHub issues | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Can you also mention or "via design partnerships.Contact your account team" or similar. Or do you think this would be implied? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Suggested change
I'm not familiar with the term There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. yeah. i think that's great There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. much better | ||||||
| Early access features are neither feature-complete nor stable. We do not | ||||||
| recommend using early access features in production deployments. | ||||||
| Coder releases early access features behind an “unsafe” experiment, where | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Suggested change
We also sometimes have early access via separate executable which is opt-in, such as the Coder Desktop binary or a module/helm install. So it is not exclusively coupled to experiments | ||||||
| they’re accessible but not easy to find. | ||||||
| They are disabled by default, and not recommended for use in | ||||||
| production as they may cause performance or stability issues. In most cases, | ||||||
| early access features are complete, but require further internal testing and | ||||||
| will stay in theearly accessstage for at least one month. | ||||||
| Coder may make significant changes or revert features to a feature flag at any time. | ||||||
| If you plan to activate anearly access feature, we suggest that you use a | ||||||
| staging deployment. | ||||||
| ```yaml | ||||||
| # Enable allearly access features | ||||||
| coder server --experiments=* | ||||||
| # Enable multipleearly access features | ||||||
| coder server --experiments=feature1,feature2 | ||||||
| # Alternatively, use the `CODER_EXPERIMENTS` environment variable. | ||||||
| ``` | ||||||
| You can opt-out of a feature after you've enabled it. | ||||||
| ### Available experimental features | ||||||
| <!-- Code generated by scripts/release/docs_update_experiments.sh. DO NOT EDIT. --> | ||||||
Uh oh!
There was an error while loading.Please reload this page.