Skip to content

Add a section for backports in the security release tracking issue

David Fernandez requested to merge 10io-update-security-release-tracking-issue into master

What does this MR do?

Update the Security Release tracking Issue template to add new section about branches that need to be targeted by the MRs in the GitLab Security project.

Rationale

I often the same confusion around the security release tracking issue which revolves around the very same question:

  • Which git branches should be targeted in the GitLab Security project MRs?

I recently mixed up the milestone in the security release tracking issue with the branches to be targeted. See https://gitlab.slack.com/archives/C0XM5UU6B/p1596703232453500 (internal).

I think the situation can be improved by adding an explicit section that states which branches GitLab Security MRs should target. Usually it should be master + the 3 previous versions.

Edited by Mayra Cabrera

Merge request reports