clarify LTS commitment - #3093
Conversation
Mostly this adds some clarity which fixes qualify to get into an LTS version and what SLO (or lack thereof) users can expect. Mark Prometheus 3.5 as end of life. Signed-off-by: Jan Fajerski <jfajersk@redhat.com>
| or documentation fixes might be added. The build toolchain will also be kept | ||
| up-to-date. This is a best effort commitment by the community, contributions are | ||
| welcome. | ||
| Support periods of two subsequent LTS version should overlap by at least one |
There was a problem hiding this comment.
This will be a contentious point as 1 month for using latest (even if LTS) version can be scary.
"Best effort" 3 months might be the same effect as "best effort" 1 month IMO, but I know we discussed not extending.
There was a problem hiding this comment.
Yeah this is not meant to address longer overlap request. The goal here is more to clarify what LTS support actually means. Based on the perhaps we can better discuss if we can handle more overlap or not.
There was a problem hiding this comment.
I do not really get this.. the whole prometheus project is best effort
There was a problem hiding this comment.
Long Term Support might encourage some people to think otherwise though. Can't hurt to make this explicit?
There was a problem hiding this comment.
I am sure the whole prometheus project is best effort this not well understood (:
Co-authored-by: Bartlomiej Plotka <bwplotka@gmail.com> Signed-off-by: Jan Fajerski <jan--f@users.noreply.github.com>
4 participants
Mostly this adds some clarity which fixes qualify to get into an LTS version and what SLO (or lack thereof) users can expect. Mark Prometheus 3.5 as end of life.
As discussed on the latest developer summit meeting.