Skip to content

docs(release): ship on a weekly Monday train - #3544

Merged
datlechin merged 1 commit into
mainfrom
docs/release-weekly-train
Oct 18, 2026
Merged

datlechin merged 1 commit into
mainfrom
docs/release-weekly-train

Conversation

@datlechin

Copy link
Copy Markdown
Member

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.
  • Branches: a line closes when X.(Y+1).0 ships; a later security or data-loss fix ships as a critical patch on the current stable line.
  • Plugins: a TABLEPRO_PLUGINKIT_VERSION bump enters a line only at beta.1.
  • Release skill: section 2 reads the newest beta's age, section 3 decides by day and points to Schedule, section 6 follows the patch bar and the closed line. Phasing stays 21600 s.

Verified

  • verify.sh agent-docs passes.

@datlechin
datlechin merged commit 257aa92 into main Oct 18, 2026
18 checks passed
@datlechin
datlechin deleted the docs/release-weekly-train branch October 18, 2026 20:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant