Refactor Release Post Start task and associated templates
Ideally as part of the move to releasing GitLab on the 3rd Thursday of the Month, we'll update Release Post automation to accommodate the new distribution date.
Problem: Templates have hard coded dates. E.g., YYYY-MM-07 or “due by the 15th" or “Please add your feedback by YYYY-MM-DD”.
Proposed Solution: To maintain similar functionality that we have today, we’ll need to make these dates in the template more dynamic and relative to the release Thursday.
- Refactor .gitlab/merge_request_templates/Release-Post.md
- Refactor .gitlab/issue_templates/Release-Post-Retrospective.md
- Refactor lib/tasks/release_post.rake to
- Add method(s) to use the release post dates replacing due dates with relative dates. 7, 5, 4, 3, 2, 1, 0 days out from the release date.
- Possibly process the MR template file with ERB rather using gsub methods
Workaround as noted in &2215 (comment 1508609516): The Release Post Manager could update all of these sections manually.
Related issue: #34226 (closed)
Edited by Ian Pedowitz