Update schedule.json to reduce v25.x Maintenance #1108
+1
−1
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. For example, we did release Node.js 23.11.1 after Node.js 24.0.0, which takes probably more volunteer time that it brings value to the community.
I suggest we reduce the maintenance window, I picked 2026-05-06 because 24.0.0 was released on 2025-05-06 (so as long as 26.0.0 is not as delayed as 24.0.0 was, we don't have a gap where v25.x is EoL before v26.x is released).
wdyt?