Proposal for adding "timeline" and "corrective actions" to the tracking issues for releases
This issue is to propose that we do away with separate retrospective issues for releases, the reason is that they are always necessary (right now) and that it adds a bit of overhead. We should also make the "release timeline" something that is required from the beginning of the release
This would affect the release templates
- security release - https://gitlab.com/gitlab-org/gitlab-ce/blob/master/.gitlab/issue_templates/Security%20Release.md
- monthly release - https://gitlab.com/gitlab-org/release-tools/blob/master/templates/monthly.md.erb
- patch release - https://gitlab.com/gitlab-org/release-tools/blob/master/templates/patch.md.erb
It does not include the release candidate release (https://gitlab.com/gitlab-org/release-tools/blob/master/templates/release_candidate.md.erb) since this would be covered by the monthly release issue.
The proposal is that in place of having a retrospective issue we add the following sections to this templates:
## Timeline
## Corrective Action
Where the timeline would have the format of
- YYYY-MM-DD [RC#] <item>
In the timeline goes any problem encountered during the release that results in the RM going "off-script", such as red pipelines that require intervention, failed deployments, etc.
For items that are "on-script", the checkboxes suffice (like deployments, merges etc).