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 allows 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 name suggestion based on the project's last release:
- Semver:
v1.2.0becomesv1.3.0 - Calver:
2026.5becomes2026.6 - ISO date:
2026-05-05becomes today's date - Human dates:
May 2026becomesJune 2026 - Sprint patterns:
Sprint 47becomesSprint 48
Custom names like MVP or Beta get no suggestion. Just type whatever you want.
A release also takes a markdown description, an optional target date, 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 sits 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
New tasks auto-assign to the current active release, so you don't have to think about release attachment every time. Override it in the create-task modal, or change it later from the task properties dropdown.
Deleting a release
Deleting a release detaches its tasks rather than deleting them. They stay in the project, unattached, and you can re-attach them to another release from the task modal.
Tasks are the work; releases are the planning shell around them. 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. - To send users polished notes when a release ships, try the Release notes generator.