From 4fa2dfe72ed472aa5a91aa4e2e9b7bb984512fbf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20K=C4=99pie=C5=84?= Date: Thu, 16 Jul 2020 11:28:09 +0200 Subject: [PATCH] Update release checklist Add an item to the release checklist to make sure confidential issues assigned to the relevant milestone are made public after the BIND versions addressing them are released. --- .gitlab/issue_templates/Release.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitlab/issue_templates/Release.md b/.gitlab/issue_templates/Release.md index d9fb8f30aa..26d7a0c76a 100644 --- a/.gitlab/issue_templates/Release.md +++ b/.gitlab/issue_templates/Release.md @@ -67,6 +67,7 @@ - [ ] ***(SwEng)*** Push tags for the published releases to the public repository. - [ ] ***(QA)*** For each maintained branch, update the `BIND_BASELINE_VERSION` variable for the `abi-check` job in `.gitlab-ci.yml` to the latest published BIND version tag for a given branch. - [ ] ***(QA)*** Prepare empty release notes for the next set of releases. + - [ ] ***(QA)*** Sanitize all confidential issues assigned to the release milestone and make them public. - [ ] ***(QA)*** Update QA tools used in GitLab CI (e.g. Flake8, PyLint) by modifying the relevant `Dockerfile`. [^1]: If not, use the time remaining until the tagging deadline to ensure all outstanding issues are either resolved or moved to a different milestone.