From da6a4bec21767683692c7e9071895b005ff15dca Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20K=C4=99pie=C5=84?= Date: Thu, 21 May 2020 09:14:27 +0200 Subject: [PATCH] Update release checklist - First merge release branches to maintenance branches, then push tags. If tags are pushed first and a given set of releases contains security fixes, the push will be rejected by a server-side Git hook. - Update ABI check job name. - Add an item for updating QA tools used in GitLab CI after each public release. --- .gitlab/issue_templates/Release.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.gitlab/issue_templates/Release.md b/.gitlab/issue_templates/Release.md index 8384fbe71d..d9fb8f30aa 100644 --- a/.gitlab/issue_templates/Release.md +++ b/.gitlab/issue_templates/Release.md @@ -63,10 +63,11 @@ - [ ] ***(Marketing)*** Update [Wikipedia entry for BIND](https://en.wikipedia.org/wiki/BIND). - [ ] ***(Marketing)*** Write blog article (if a major release). - [ ] ***(QA)*** Ensure all new tags are annotated and signed. - - [ ] ***(SwEng)*** Push tags for the published releases to the public repository. - [ ] ***(SwEng)*** Merge the automatically prepared `prep 9.X.Y` commit which updates `version` and documentation on the release branch into the relevant maintenance branch (`v9_X`). - - [ ] ***(QA)*** For each maintained branch, update the `BIND_BASELINE_VERSION` variable for the `abi-check:sid:amd64` job in `.gitlab-ci.yml` to the latest published BIND version tag for a given branch. + - [ ] ***(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)*** 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.