Adapt the security release template to account for the new release date
Starting on 16.6, the monthly release date will be moved from the 22nd to the 3rd Thursday of each month (details on &1039 (closed)). To prepare for this change, the security release should be adapted to the new dynamic date-
Exit criteria
-
Update the TrackingIssue#due_date
logic: If the feature flag (dynamic_release_date
) is enabled, a due date should not be set. -
Remove the hardcoded dates from the security templates. For example: On the 25th (three days before due date
), should beThree dates before the due date
. -
Add a step on the security template asking release managers to assign the dates. -
Template changes should be under a feature flag. -
Remove the Slack reminder for security releases. - Note: The reminder can be removed since we have a step on the monthly template to schedule the date. https://gitlab.com/gitlab-org/release-tools/-/blob/master/templates/security_patch.md.erb#L193
Note: There is a follow-up to automatically assigned dates based on &1073 (closed)
Edited by Mayra Cabrera