You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[docs] Formalize the SemVer tag and daily release policy #271
Write the existing OpenDirector tag and daily release practice into the repository so cuts are not only tribal knowledge.
Current published tags: v0.1.0, v0.1.1, and v0.1.2, each with a GitHub Release. In-tree version fields stay at the last cut (currently 0.1.2) until the next one lands.
Related: #7 (release readiness go/no-go). This issue does not replace #7.
Policy to record
Public tags use SemVer with a v prefix: vMAJOR.MINOR.PATCH. Do not introduce a second public stream (CalVer, date tags, or nightly tags).
Daily patch cuts stay on v0.1.x around 04:00 Asia/Shanghai after the ~02:00 nightly, when there are merges since the last tag and Release checks plus the last nightly gate-parity are green. Skip if there are no merges, or if that gate is red or still running. Advisory nightly lanes (browser-production, browser-extended, perf-outputs) do not block.
Bump MINOR only for a named milestone. Bump MAJOR only when declaring a supported public product (v1.0.0).
Each published tag is immutable, points at one main SHA (after the version-bump PR), and ships a GitHub Release with English notes listing merges since the previous tag. Do not retag, and do not create a floating latest git tag.
Nightly CI is a gate, not a public release. If installable nightlies are added later, they must be GitHub prereleases (for example v0.1.3-nightly.YYYYMMDD) and must not become the repository's latest release.
Deliverable
Add docs/development/release.md with the policy above, short and operational.
Policy update (Hongsheng, 2026-11-11): the public SemVer stream is not frozen on v0.1.x.
Daily patch cuts continue on the current minor (v0.N.x) around 04:00 Asia/Shanghai, with the same gate (Release checks plus the last nightly gate-parity lane). Skip a patch morning when there are no merges, or when that gate is red or still running. Advisory nightly lanes still do not block.
Every 2 weeks, cut a minor (“big release”): v0.2.0, v0.3.0, and so on, at the same morning window. Use the same version-field alignment and an English GitHub Release. On a minor-cut morning, that cut is v0.(N+1).0, not another patch; daily patches then continue on the new minor.
If the gate is red or still running when a minor is due, delay that minor until the gate is green. Do not skip the minor, and do not cut it with a red gate.
MAJOR remains v1.0.0 only when declaring a supported public product.
Still one public tag stream. Do not add CalVer, date tags, or nightly public tags.
Activity
hsliuustc0106 commentedon Nov 11, 2026
Policy update (Hongsheng, 2026-11-11): the public SemVer stream is not frozen on
v0.1.x.v0.N.x) around 04:00 Asia/Shanghai, with the same gate (Release checks plus the last nightlygate-paritylane). Skip a patch morning when there are no merges, or when that gate is red or still running. Advisory nightly lanes still do not block.v0.2.0,v0.3.0, and so on, at the same morning window. Use the same version-field alignment and an English GitHub Release. On a minor-cut morning, that cut isv0.(N+1).0, not another patch; daily patches then continue on the new minor.v1.0.0only when declaring a supported public product.#272 will be updated to match.
[docs] release: record SemVer tags and daily cuts
[docs] release: cut a minor every 14 days
Record SemVer daily patches and the 14-day minor (ThinkFlowLab#272)