chore: schedule the next maintenance rounds - #121
Merged
Merged
Conversation
Signed-off-by: nextcloud-bot <bot@nextcloud.com>
skjnldsv
force-pushed
the
chore/release-schedule
branch
from
September 11, 2026 09:01
cf8e046 to
c1f7060
Compare
skjnldsv
enabled auto-merge
September 11, 2026 09:01
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
2 participants
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.
release-schedule.jsonis short of the dates the next releases need. The milestones step requires a date for the next patch milestone of the series being released, and fails on release day without one, leaving the released milestone open and its issues unmoved.This keeps two future rounds dated for every major still inside its 12-month maintenance window, and drops entries for rounds that have shipped.
Important
These dates come from the cadence documented in the README: a Thursday, one per calendar month, four weeks on and five when four would land twice in one month. They are not read from the wiki. Check them against the wiki release schedule before merging and edit this pull request wherever they differ.
Entries that already had a date were left alone, so a correction made by hand survives. Nothing is scheduled past a major's maintenance window.