-
Notifications
You must be signed in to change notification settings - Fork 110
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
Change in Prometheus2 release cycle #703
Comments
@RainbowHerbicides, do you know if there can be multiple Prometheus LTS releases in parallel? |
@karlism I am not 100% sure but judging by their announcement and their schedule https://github.com/prometheus/prometheus/blob/main/RELEASE.md#release-schedule - current LTS ( |
Tried asking in IRC and on Twitter - received 0 reply |
6 months : https://prometheus.io/docs/introduction/release-cycle/ & https://github.com/prometheus/prometheus/releases/tag/v2.37.0 And this only concerns the server part This could cause the repository to be split into three parts (lts, release, common) |
Prometheus decided to introduce LTS releases with
2.37.0
https://prometheus.io/docs/introduction/release-cycle/, which will not fit with current repository structure. I propose to make a copy ofhttps://github.com/lest/prometheus-rpm/tree/master/prometheus2
but under different nameprometheus2-lts
and bump versions specifically for2.37.X
releases (2.37.1 already out but not obtainable through this repo). Compiled package could have the same nameprometheus2
but description that will reflect that this is LTS release.The text was updated successfully, but these errors were encountered: