-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[Backport 2.28] Clarify LTS lifetime #7409
[Backport 2.28] Clarify LTS lifetime #7409
Conversation
Signed-off-by: Janos Follath <[email protected]>
Co-authored-by: Gilles Peskine <[email protected]> Signed-off-by: Janos Follath <[email protected]>
BRANCHES.md
Outdated
Every major version will become an LTS branch when the next major version is | ||
released. We may occasionally create LTS branches from other releases at our | ||
discretion. | ||
After a new LTS branch is created, it remains supported for at least 3 years. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence is different in development, is that deliberate?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it wasn't. I forgot to backport Dave's suggestion. Thanks for catching this.
Co-authored-by: Dave Rodgman <[email protected]> Signed-off-by: Janos Follath <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
Backport of #7383.
Users can get more value out of our LTS releases and plan transition between versions better if the documentation is more clear about the lifetime of LTS branches.
Gatekeeper checklist