Work as a team
Releases on the calendar
What ships when: planned releases, the moves that happened, no-release days, public holidays and who is away, on Calendar.
Open Releases on the calendar in the appWhat it shows
Open Calendar and pick Releases. For each environment it shows:
- planned releases: a system, a version or a name, the environment, a day or a few days, and the team;
- moves: every release that reached the environment, written by the move itself (with the teams it moved without, if any);
- no-release days, with their reason;
- public holidays, and how many people in a planned release's team are away that week.
Coming up lists what is ahead, soonest first, with Earlier below it. Week and Month show a grid. Press Filter to see one environment, team or system; Key explains the colours and icons. The old Release calendar link opens this view.
Plan a release
- Press Plan a release, or click a day's number.
- Pick a system, the environment and the days. Add the version if you know it; the title becomes "Orders 2.4.0".
- Press Save.
When a release with that version moves to the environment, the plan shows Moved and when. After its days, a plan whose release never moved shows Late: not moved yet. From a planned release you can Ask the affected teams to sign off before it moves.
No-release days
Whoever manages environments presses No-release days (or Add → Add no-release days), picks an environment and the days, and says why ("Year-end freeze"). A move into the environment on one of them shows a warning on the move request and in the safety check. Tick Block moves on these days and only Move anyway, with a reason, moves a release then; the reason is recorded. Everyone can open the list.
Who may change it
Planning a release is for whoever may make releases; no-release days for whoever manages environments. Everyone in the project sees them.
What is kept
The last 500 moves, planned releases for half a year after their days, and no-release days for a year. Older moves are under Deployments.
Related
- Sign-off from affected teamsWhen a release changes or breaks the calls other teams make, those teams are asked to sign off before it moves; every answer and every move without one is recorded.
- Time awayMark when people are away, add public holidays, and pick who covers, so sign-offs and team issues reach someone who is here.
- Versions and releasesRun API versions side by side, read the history and diff of every endpoint, create releases with a suggested version, and check old copies.
- Environments and deploymentsRecord which release of each system runs in each environment, see compatibility per environment, and check a release before you deploy it.
