Commit 5a3b5e08 authored by Tobias Schmidt's avatar Tobias Schmidt

Fix stable/unstable list headers in 1.0 post

parent f2c8af99
......@@ -14,7 +14,7 @@ We’re thrilled to announce that we’ve reached this goal, and [Prometheus 1.0
## What does 1.0 mean for you?
If you have been using Prometheus for a while, you may have noticed that the rate and impact of breaking changes significantly decreased over the past year.
In the same spirit, reaching 1.0 means that subsequent 1.x releases will remain API stable. Upgrades won’t break programs built atop the Prometheus API, and updates won’t require storage re-initialization or deployment changes. Custom dashboards and alerts will remain intact across 1.x version updates as well.
In the same spirit, reaching 1.0 means that subsequent 1.x releases will remain API stable. Upgrades won’t break programs built atop the Prometheus API, and updates won’t require storage re-initialization or deployment changes. Custom dashboards and alerts will remain intact across 1.x version updates as well.
We’re confident Prometheus 1.0 is a solid monitoring solution. Now that the Prometheus server has reached a stable API state, other modules will follow it to their own stable version 1.0 releases over time.
### Fine print
......@@ -22,7 +22,8 @@ We’re confident Prometheus 1.0 is a solid monitoring solution. Now that the Pr
So what does API stability mean? Prometheus has a large surface area and some parts are certainly more mature than others.
There are two simple categories, _stable_ and _unstable_:
* Stable as of v1.0 and throughout the 1.x series:
Stable as of v1.0 and throughout the 1.x series:
* The query language and data model
* Alerting and recording rules
* The ingestion exposition formats
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment