Skip to content

docs(guarantees): update stable component criteria #25681

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.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pront merged 1 commit into from
Jun 25, 2026
+4 −7
Merged

docs(guarantees): update stable component criteria #25681

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions website/content/en/docs/architecture/guarantees.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,13 +92,10 @@ The `stable` status is a _subjective_ status defined by the Vector team. It's in
general idea of a feature's suitability for production environments. A feature is considered stable
if it meets the following criteria:

1. A meaningful number of users (generally over 50) have been using the feature in a production
environment for a sustained period of time without issue.
2. The feature has had sufficient time (generally more than 4 months) to be community tested.

3. The feature API is stable and unlikely to change.

4. There are no major [open bugs][bugs] for the feature.
1. The feature has had sufficient time (generally more than 4 months) to be community tested.
2. The feature API is stable and unlikely to change.
3. There are no major [open bugs][bugs] for the feature.
4. There is positive community signal that the feature is being used successfully in production environments.

### Beta

Expand Down
Loading