For developers · Orchestrator
Release planning
Scope#
Per repository, an issue belongs to the next release when
- it carries
release:next(reasonlabel), or - it carries
priority:p0(reasonpriority; the label wins when both are set), or - it is a dependency, recursively, of a member (reason
dependency).
Only dependencies inside the same repository count. Open and closed issues are considered
together, so a finished dependency stays part of the release. The legacy labels release:muss and
release:später have no effect.
Planning is switched per repository with releases in the orchestration config (default on).
With it off, the repository has no scope, no bonus and does not appear in the views.
Score#
Every scope member gets the release bonus (score.release_bonus, spec 7.1 item 4), whatever the
reason. Dependencies therefore rank with the issues that need them.
States#
| state | meaning |
|---|---|
open | open, nobody works on it |
in-progress | open with in-progress/in-review or a lease holder |
merged | closed and the ledger holds a completed lease by the bot (worker result merged) |
closed | closed without a completed lease (by hand, won't do) |
Items are ordered open, in-progress, merged, closed, then by number.
Assumption: release:next labels are removed when a release is cut. The cut itself is not part of
v1; until then the view shows the whole history of the label.
Surfaces#
- CLI:
gitoodo release [--repo owner/name] [--json]. - MCP tool
ledger_release_status(optionalrepo). - Tauri command
release_status(repo?: string), all three return the same report:
{
"polled_at": "rfc3339 or null",
"repos": [
{
"account_id": "...",
"full_name": "owner/name",
"release": {
"enabled": true,
"items": [
{
"number": 1,
"title": "...",
"html_url": "...",
"state": "open | in-progress | merged | closed",
"reason": "label | priority | dependency"
}
]
}
}
]
}The read model (orchestrator_read_model) carries the same data per repository as release.
App#
Release planning is the first, collapsible section of the board (#518;
dashboard-orchestrator-release-toggle, panel dashboard-orchestrator-release, closed by default and
remembered). Open, it shows the release panel (release). Per repository with planning on it shows the progress (merged and closed of all items,
as text and bar) and the items ordered open, in progress, merged, closed, each with its state and
the reason it belongs to the release; a click opens the item in the board sheet, from where the
forge page is an explicit secondary action. The panel fetches
release_status on open, every 30 seconds and via release-refresh; a failed fetch shows
release-error and keeps the last picture. Without any repository planning a release it shows
release-empty with the hint to switch on releases in orchestration.json. Test ids: release-*
(release-repo-<repo>, release-progress-<repo>, release-item-<repo>-<number>; / in the repo
name becomes -).