Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

internal: migrate to standard Grafana stability definitions #92

Merged
merged 2 commits into from
Mar 27, 2024

Conversation

rfratto
Copy link
Member

@rfratto rfratto commented Mar 27, 2024

This commit changes the stability levels to align with Grafana's standard set:

  • Experimental / experimental (unchanged)
  • Public preview / public-preview (previously "beta")
  • Generally available / generally-available (previously "stable")

cc @clayton-cornell I didn't update any of the docs here, since I'm guessing we'll need a bit of thought about how we reflect this in the docs.

Also I noticed that the --stability.level flag isn't publicly documented anywhere; I added a task for us to document that prior to the 1.0 release.

This commit changes the stability levels to align with [Grafana's
standard set][1]:

* Experimental / `experimental` (unchanged)
* Public preview / `public-preview` (previously "beta")
* Generally available / `generally-available` (previously "stable")

[1]: https://grafana.com/docs/release-life-cycle/
@clayton-cornell
Copy link
Contributor

Yes this is definitely an action item for Alloy. Since we are using the standard release life cycle, I think the easiest is to simply link out to this external topic.

We need to make sure that stability/beta and stability/experiments shared topics are updated. PR for this is: #93

@rfratto
Copy link
Member Author

rfratto commented Mar 27, 2024

Merging; I'll follow up wit ha PR to document --stability.level

@rfratto rfratto merged commit 0a388b9 into main Mar 27, 2024
9 checks passed
@rfratto rfratto deleted the use-standard-grafana-stability-definitions branch March 27, 2024 19:08
@rfratto rfratto added the backport-to-agent:no PR should NOT be backported to the agent repo. label Apr 23, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 24, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport-to-agent:no PR should NOT be backported to the agent repo. frozen-due-to-age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants