fix: keep NC35 on the October maintenance round - #127
Merged
Merged
Conversation
v35.0.1rc1 was tagged 2026-09-20, three and a half weeks before the 2026-10-15 date its schedule entry carries. The schedule maps version numbers to dates and SchedulePlan never re-dates an existing entry, so 35.0.2 kept 2026-11-12 and the 2026-10-15 round was left with no NC35 release while 33 and 34 both ship on it. Move 35.0.2 onto 2026-10-15. schedule:extend derives 35.0.3 as 2026-11-12 from there, and milestones:update applies the corrected date to the Nextcloud 35.0.2 milestone when 35.0.1 ships. Assisted-by: ClaudeCode:claude-opus-5 Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
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
1 participant
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.
v35.0.1rc1was tagged 2026-09-20, three and a half weeks ahead of the 2026-10-15 date its schedule entry carries. The schedule maps version numbers to dates andSchedulePlannever re-dates an existing entry, so 35.0.2 stayed on 2026-11-12 and the October round was left with no NC35 release:Moving 35.0.2 onto 2026-10-15 is enough, the cadence derives the rest:
I kept 35.0.3 and the removal of the shipped 35.0.1 out of the diff, since
schedule:extend --writeadds both on its next run.Important
This wants to merge before 35.0.1 stable ships.
milestones:updatereads the schedule at release time and applies the due date to theNextcloud 35.0.2milestone, which currently says 2026-11-12. Merged first, the milestone self-corrects. Merged after, someone fixes that milestone by hand.This repairs the one instance, it does not change the tooling. Any off-date release still consumes a version number without consuming a calendar slot, and the missing round stays silent. Worth a follow-up in
ScheduleRefresh::applyMajor(), which already has both the scheduled anchor and the version in flight and could warn when they diverge.👾 This pull request was assisted by Claude Code, commits carry an
Assisted-bytrailer.