Releases and readiness
Plan a version, link the tasks that ship in it, and read whether it is ready — tasks done, tests passing — with a changelog you can copy.
A release is a named version and the tasks that ship in it. From that set Rindo derives its progress, its readiness, a test pass rate, the pull requests involved and a changelog. It never decides when you ship; it says what the record says. The Releases tab is in the project when its template included the releases module.
Create a release
Choose New release: a Version name (required, unique in the project — v1.2.0), and optionally a Title for display, a Description and a Target date. A new release is in Planning.
Status
- Planning and Active are the two working states; Mark active and Back to planning move between them, and several releases can be active at once.
- Mark released… freezes the linked task set — nothing can be linked or unlinked any more — and makes the release read-only.
- Cancel release… makes it read-only too, and a cancelled release cannot be reopened. There is no delete: cancelling is how a release ends.
A planning or active release past its target date reads overdue in the list.
Link tasks
On the release page, Link task searches tasks or takes a key, and Unlink removes one — while the release is planning or active. A task may be in several releases; the task page lists them. Over MCP your assistant links and unlinks the same way, and can list a release’s tasks.
Readiness
The card at the top of the release reads Ready or Not ready, from two checks:
- Tasks — the card reads N/M linked tasks done: every linked task sits in a status of the done category (so the default Cancelled status counts as done — see Project overview). A release with no linked tasks is not ready: No linked tasks — link tasks to track readiness.
- Tests — the Active test cases linked to the release’s tasks. Tests passing means each one’s latest result, from any run, is a pass. A case that has never been run, or whose latest result is a fail, a skip or a block, makes it Tests failing. With no active linked cases the check reads No active linked test cases and neither blocks nor passes.
A third line, Docs updated — not tracked yet, is shown and never evaluated. The release is ready when the first check holds and the second is not failing. At the foot of the card, Pending tasks lists up to fifty tasks not yet done.
The figures
- Progress — the share of linked tasks that are done, by count: 45% · 9/20.
- Tests — the share of the same case set whose latest result is a pass; — when there are no active linked cases.
- Pull requests — N of M merged, from the pull requests linked to the release’s tasks through a connected repository (see GitHub and GitLab). They are listed under Linked pull requests with their state. Pull requests inform; they do not enter readiness.
Changelog
The Changelog is generated from the done linked tasks — tasks in the Cancelled status included, since that status is in the done category — grouped by work item type in the types’ order, with the target date when one is set:
# v1.2.0
_Target date: 2026-11-01_
## story
- **ACME-12** Payment retries
A release with no done task prints No completed tasks. Copy markdown takes the text to your clipboard; the same text is what an assistant gets over MCP. It is not edited in Rindo — paste it where your release notes live.
Who can do what
Everyone in the project reads releases, their readiness and their changelog. Creating, editing, changing status, linking and unlinking take Member; a project agent can link and unlink too, unless its scope leaves out Move sprints and releases. Creating a release, editing one or changing its status has no MCP tool: an assistant lists releases with their status, target date and progress, links tasks, and reads the changelog.