Releases
The active-release model. One release is "now". Smart name suggestions, lifecycle stages, and drag-drop reordering.
A release is what you're shipping next. Frostbyte enforces a single active release per project, the most opinionated decision in the model. It exists to answer "what are we shipping next?" in under a second.
The lifecycle
Every release moves through three stages:
- Upcoming, planned but not yet being worked on.
- Active, the release that "now" means. Only one per project.
- Completed, shipped. Closed for new work; tasks stay visible for history.
Setting a release as active automatically demotes the previous active release to upcoming. The change syncs in real time across every connected session.
Creating a release
Click New release from the Releases page. You'll get a smart name suggestion based on the project's last release:
- Semver:
v1.2.0→v1.3.0 - Calver:
2026.5→2026.6 - ISO date:
2026-05-05→ today's date - Human dates:
May 2026→June 2026 - Sprint patterns:
Sprint 47→Sprint 48
Custom names like MVP or Beta get no suggestion — just type whatever you want. The smart-name helper is deterministic, so the same input always produces the same suggestion.
A release also takes a description (markdown), a target date (optional), and a status. New releases default to upcoming; promote them to active when you start working.
The Releases page
The Releases page shows three columns: Active, Upcoming, Completed. The active release lives in a dedicated hero zone at the top with the in-progress and to-do tasks that need attention right now.
Each release card has an inline action menu: Edit, Set as active, Delete. Drag-and-drop reorders releases within a column.
Default release on new tasks
When you create a new task, it auto-assigns to the current active release. This means you don't have to think about release attachment for every task, just create them and they land in the right place.
You can override the release in the create-task modal or change it later via the task properties dropdown.
Deleting a release
Deleting a release detaches its tasks (sets releaseId to null), it does not delete the tasks. They remain in the project, just unattached. You can re-attach them to another release from the task modal.
This is intentional: tasks are the work, releases are the planning shell. Removing a release shouldn't lose work.
What's next
- See how tasks tag to releases: Tasks.
- If you ship from
main, wire up the GitHub integration so commits and PRs auto-link to release tasks. - If you're on Basic+ and want to send users polished release notes, try the Release notes generator.