Tier 0 — ~30 minutes.
The public releases list currently reads:
| Published |
Tag |
| 2026-08-08 |
nightly |
| 2026-03-27 |
v5.0-beta.2026 |
| 2023-10-30 |
v5.0-beta.2023 |
| 2023-05-05 |
v5.0-beta.ZZZ.2023lunch |
| 2022-10-12 |
v5.0-beta.ZZZ |
| 2022-09-04 |
v5.0-beta.ZZZ.RC1 |
v5.0-beta.ZZZ.2023lunch is visible to everyone who opens the releases page or the sidebar.
Why it matters
The releases sidebar is one of the first things an evaluator checks for signs of life. Placeholder tags read as an unmaintained internal project. The repo was created in 2012 and every release is still labelled beta — to an outside reader that is fourteen years without a stable release, which is not the story we want to tell.
Action
- Retitle the historical releases (the display name can be changed without moving the tag) so
ZZZ and 2023lunch are not user-facing.
- Decide what the beta label is actually gating. If nothing concrete remains, cut a
v5.0.0. If something does, name it in the release notes so the label means something.
- Give the
nightly rolling release a description that says what it is and who should use it.
Related: the release-notes and packaging work already tracked elsewhere in the 5.0.0 milestone.
Tier 0 — ~30 minutes.
The public releases list currently reads:
nightlyv5.0-beta.2026v5.0-beta.2023v5.0-beta.ZZZ.2023lunchv5.0-beta.ZZZv5.0-beta.ZZZ.RC1v5.0-beta.ZZZ.2023lunchis visible to everyone who opens the releases page or the sidebar.Why it matters
The releases sidebar is one of the first things an evaluator checks for signs of life. Placeholder tags read as an unmaintained internal project. The repo was created in 2012 and every release is still labelled beta — to an outside reader that is fourteen years without a stable release, which is not the story we want to tell.
Action
ZZZand2023lunchare not user-facing.v5.0.0. If something does, name it in the release notes so the label means something.nightlyrolling release a description that says what it is and who should use it.Related: the release-notes and packaging work already tracked elsewhere in the 5.0.0 milestone.