Skip to content

Update monthly release template

Steve Abrams requested to merge delivery2823-add-monthly-release-step-to-update-stable-ci into master

What does this MR do and why?

As described in gitlab-com/gl-infra/delivery#2823, we only want to send slack notifications and open broken branch issues for stable branch failures if the branch is part of the extended maintenance policy (last 3 versions). Unfortunately, dynamically determining these versions in the .gitlab-ci.yml file is not something we can easily do right now. So for the first iteration, we have a CI rule that creates pipelines that will send slack notifications based on a hardcoded regex targeting the branches in the maintenance policy.

This MR adds a step to the monthly release template to update that regex to the new active versions (remove the oldest version and add the version that was just released).

The MR that adds the initial hard-coded versions is gitlab!111645 (merged). So the issue for the 15.10 release will be the first one where we will need to update these values.

Author Check-list

  • [-] Has documentation been updated?

Merge request reports