Update schedule.json to reduce v26.x Maintenance #1109
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've discussed in the Release WG meeting about how having long maintenance put a too heavy burden for security releases. One proposal was to reduce the Maintenance window so we don't end up in a situation where we have 4 non-EoL release lines to maintain (as it is the case currently, with up to 5 even for a brief period of the year).
I don't know if we want to do that for every LTS lines, or rather every two years (i.e. 26.x 2.5 years of support, 28.x 3 years, 30.x 2.5 years, 32.x 3 years, etc.), and it's obviously hard to predict where the project will be in 2029, but it's probably better to discuss it now so consumers can adapt.
wdyt?