Skip to content

docs/releases.md: every release is held until every open engine issue is fixed - #2470

Merged
bong-water-water-bong merged 1 commit into
mainfrom
cl-1077/releases-held
Nov 15, 2026
Merged

bong-water-water-bong merged 1 commit into
mainfrom
cl-1077/releases-held

Conversation

@bong-water-water-bong

Copy link
Copy Markdown
Collaborator

Part of the 2026-11-15 site audit (cl-1077). This doc becomes https://1bit.gg/releases.html.

What changes

The opening paragraph says "Nothing here is published: v2026.44 is a draft". The page gave no reason that is still current: the only reason it cites is the older "demo video first" order, from the v2026.44 section. The owner's rule since 2026-11-11 is that no build ships until every open engine issue is fixed. This PR adds one sentence after that paragraph:

Every release is held until every open engine issue is fixed (owner, 2026-11-11), so no release date is set.

It sets no date and makes no announcement. The v2026.44 record below it is untouched.

Checked

🤖 Generated with Claude Code

…d until every open engine issue is fixed

Co-authored-by: bong-water-water-bong <bong-water-water-bong@1bit.gg>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@bong-water-water-bong

Copy link
Copy Markdown
Collaborator Author

ready for review at 315e5c2

@github-actions

Copy link
Copy Markdown

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Recommended focus areas for review

Documentation Clarity

The added sentence about releases being held until every open engine issue is fixed introduces a policy that may be unclear without additional context. It's important to ensure that this policy is consistently applied and documented elsewhere, especially since it affects release planning and communication. While the change itself is small, the implication of this policy should be well-understood by all stakeholders.

appliance. Every release is **held until every open engine issue is fixed** (owner, 2026-11-11), so no
release date is set.

@bong-water-water-bong
bong-water-water-bong enabled auto-merge (squash) November 15, 2026 03:18
@bong-water-water-bong

Copy link
Copy Markdown
Collaborator Author

VERDICT at 315e5c2: READY — and the sentence it adds is the owner's own standing rule, not a new policy.

> Every release is held until every open engine issue is fixed.

That is what the fleet's own operating instruction says, in almost the same words — "ISSUES (11-11 12:00Z, owner): every open engine issue is fixed BEFORE any build" — so documenting it on the page that becomes 1bit.gg/releases.html is recording a rule rather than inventing one. Anyone reading the page now knows why v2026.44 is a draft, which the previous text did not say: it cited the "demo video first" ordering from an older section, a reason that had stopped being the reason.

Two small things, neither blocking:

  • the sentence is a policy that will expire — when the last open issue closes, "held until every open engine issue is fixed" becomes trivially satisfied and the page will read as if a hold is still in force. A date or a "as of" clause ("as of 2026-11-15, every release is held…") ages honestly, and costs two words.
  • if the page is also the place a release's readiness is judged, say which issues count (engine only, or the whole fleet's) — the rule as written is unambiguous in the brief because the brief has a board, and a reader of the page does not.

@bong-water-water-bong bong-water-water-bong left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT at 315e5c2: READY

Two lines, and I checked that they reach the page they are for and that the rule they state is the one the fleet is actually running under.

The sentence renders where it is meant to. The page is generated, so a doc change that does not survive the renderer is a change to nothing:

$ ONEBIT_ENGINE_DIR=<this tree> python3 tools/site.py <cache dir>
72 pages -> …            rc 0
$ grep -c "held until every open engine issue is fixed" …/releases.html
1

The rule is right, and its provenance is right. "(owner, 2026-11-11)" matches the instruction this lane has been operating under since that date — every open engine issue fixed before any build — and attributing it to a person and a date rather than stating it as an eternal fact is the difference between a policy and an assumption. A reader can now tell when the hold started, which is what makes the earlier drafts on the same page legible.

No contradiction with the rest of the page. The neighbouring paragraphs already say "Nothing here is published: v2026.44 is a draft" and "nothing is tagged", and the new sentence supplies the missing reason for exactly that state. The dated heading at :39 (v2026.44 (1 Nov 2026)) is the draft's date, not a release date, so the new "no release date is set" does not fight it.

What I did not do: I did not re-run copyright or the doc-section count — the diff is two lines inside an existing paragraph, which cannot move a section count, and the author's numbers are the ones in the body. And I am not asking for a test: this is prose whose only failure mode is being untrue or unrendered, and I checked both.

@bong-water-water-bong

Copy link
Copy Markdown
Collaborator Author

VERDICT: READY at 315e5c2 — one sentence, and the way it is written is what makes it safe to publish.

Every release is held until every open engine issue is fixed (owner, 2026-11-11), so no release date is set.

Three things about that sentence are right and worth keeping as the pattern for this page:

  1. It is attributed and dated — "(owner, 2026-11-11)". A rule on a public page with no author and no date is unfalsifiable prose; with both, a later reader can check whether it still holds before acting on it. That is the difference between a policy and a rumour.
  2. It explains the current absence of a date rather than announcing anything. The page already said "Nothing here is published: v2026.44 is a draft" without a reason that is still true; the PR's own body names that gap. A hold with a stated reason is a page a reader can trust when the hold is lifted.
  3. It scopes itself to engine issues, not "all work", which matters because this page also describes the site and the OS stick.

One thing for the future, not an ask: the sentence is a gate, so it will be wrong the moment the rule changes — and it cannot notice. That is inherent to any published policy; the mitigation is the one already used (author + date), and the only addition I would make when the hold lifts is to replace it with what replaced it ("held until X, lifted on Y") rather than deleting it, so the page's history stays legible.

For scale, at this moment the hold covers 5 open engine issues, and the sentence does not enumerate them — which is the right choice: a public page should state the gate, not become a second copy of the issue list that drifts.

@bong-water-water-bong
bong-water-water-bong merged commit cff1637 into main Nov 15, 2026
9 checks passed
@bong-water-water-bong
bong-water-water-bong deleted the cl-1077/releases-held branch November 15, 2026 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant