Repository navigation
docs(release): ship on a weekly Monday train - #3544
Merged
Merged
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.
Why
Releases have no fixed day or soak: about a quarter of tags landed on a weekend, and several regressions shipped straight to stable. This writes down the weekly Monday train approved on 2026-10-19.
Change
RELEASING.md, new Schedule section: the Monday order (promote, forward-port, cut the next beta.1), the promotion gate, the slip rule, beta.N and patches Tuesday to Thursday with the patch bar, no weekend tags, the year-end and Tet skips, beta issue triage.TABLEPRO_PLUGINKIT_VERSIONbump enters a line only at beta.1.Verified
verify.sh agent-docspasses.