opensource/coder
3
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2026-09-24 15:04:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: document new feature stages (#16719)

Browse Source 
- [x] translate notes to docs
- [x] move to Home > About > Feature Stages
- [x] decide on bullet point summaries (👍 👎  in comment)

### OOS for this PR

add support page that describes how users can get support. currently,
[this help
article](https://help.coder.com/hc/en-us/articles/25308666965783-Get-Help-with-Coder)
is the only thing that pops up and includes that `Users with valid Coder
licenses can submit tickets` but doesn't show how, nor does it include
the support bundle docs (link or content). it'd be good to have these
things relate to each other

## preview


[preview](https://coder.com/docs/@feature-stages/contributing/feature-stages)

---------

Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com>
Co-authored-by: Ben Potter <ben@coder.com>
This commit is contained in:
Edward Angert
2025-02-26 15:43:02 -05:00
committed by GitHub
co-authored by EdwardAngert Ben Potter
parent 1cb864bc1b
commit 81ef9e9e80
3 changed files with 110 additions and 69 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/contributing/feature-stages.md
-63
View File
@@ -1,63 +0,0 @@
# Feature stages
Some Coder features are released in feature stages before they are generally
available.
If you encounter an issue with any Coder feature, please submit a
[GitHub issues](https://github.com/coder/coder/issues) or join the
[Coder Discord](https://discord.gg/coder).
## Early access features
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
they’re accessible but not easy to find.
## Experimental features
These features are disabled by default, and not recommended for use in
production as they may cause performance or stability issues. In most cases,
experimental features are complete, but require further internal testing and
will stay in the experimental stage for one month.
Coder may make significant changes to experiments or revert features to a
feature flag at any time.
If you plan to activate an experimental feature, we suggest that you use a
staging deployment.
You can opt-out of an experiment after you've enabled it.
```yaml
# Enable all experimental features
coder server --experiments=*
# Enable multiple experimental features
coder server --experiments=feature1,feature2
# Alternatively, use the `CODER_EXPERIMENTS` environment variable.
```
### Available experimental features
<!-- Code generated by scripts/release/docs_update_experiments.sh. DO NOT EDIT. -->
<!-- BEGIN: available-experimental-features -->
| Feature | Description | Available in |
|-----------------|---------------------------------------------------------------------|--------------|
| `notifications` | Sends notifications via SMTP and webhooks following certain events. | stable |
<!-- END: available-experimental-features -->
## Beta
Beta features are open to the public, but are tagged with a `Beta` label.
They’re subject to minor changes and may contain bugs, but are generally ready
for use.
## General Availability (GA)
All other features have been tested, are stable, and are enabled by default.