Update release checklist

Add an item to the release checklist to make sure regression tests
reproducing publicly disclosed security issues are eventually merged
into each maintained branch.

diff --git a/.gitlab/issue_templates/CVE.md b/.gitlab/issue_templates/CVE.md
index bff1818526ce3d75990f6498deb58b36ea8dfbb3..fc95d55ca007061093b88a6341fa0699c3e1fdf3 100644 (file)
--- a/.gitlab/issue_templates/CVE.md
+++ b/.gitlab/issue_templates/CVE.md
@@ -31,3 +31,7 @@ email to [security-officer@isc.org](security-officer@isc.org).
   - [ ] Create/update the private issue containing links to fixes & reproducers for all CVEs fixed in a given release cycle
   - [ ] Reserve a block of `CHANGES` placeholders once the complete set of vulnerabilities fixed in a given release cycle is determined
   - [ ] Ensure the merge requests containing CVE fixes are merged into `security-*` branches in CVE identifier order
+
+### Post-disclosure actions
+
+  - [ ] Merge a regression test reproducing the bug into all affected (and still maintained) BIND branches