Update monthly release template to automatically set dates for the new release schedule
The monthly release template is split into four stages: first steps, deployments, the run-up to the release, and the release date. With a dynamic release date, the 3rd Thursday of the month, these stages can be hardcoded in the release template.
The monthly release template should be updated to:
- Automatically set the release date to the respective date.
- Automatically set a date for the rest of the stages. For example, assuming that for 16.6 the release date will be 2023-11-16, the stages will be on:
- November 10th: Last commit is stored.
- November 13th: Candidate commit announced
- November 14th: Two working days before the release - Tag release candidate
- November 15th: One day before the release - Tag final version
- November 16th Release date: Release date
- Include an item in the first steps of the monthly template to request release managers to review these dates and adjust them if necessary.
- Remove the hardcoded due date, a due date is automatically set to the 25th to account for the rollback practices
- Update slack messages for the template - During the run-up to the release date, release managers notify about the candidate commit, release candidate, and stable branch creation via Slack. These messages refer to the 22nd, and they need to be updated to use the new date.
Implementation items should be under a feature flag.
Edited by Mayra Cabrera