From 5c9c53e9e768f0c0f8a30e8d996743a4a2fd5c6c Mon Sep 17 00:00:00 2001 From: Stephen Morris Date: Tue, 20 Nov 2018 14:38:35 +0000 Subject: [PATCH] Updates to BIND release checklist. --- .gitlab/issue_templates/release.md | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-) diff --git a/.gitlab/issue_templates/release.md b/.gitlab/issue_templates/release.md index 101edddf36..eb5711b2ba 100644 --- a/.gitlab/issue_templates/release.md +++ b/.gitlab/issue_templates/release.md @@ -1,19 +1,21 @@ ## Release Checklist - - [ ] (Manager) Check for the presence of a milestone for the release. + - [ ] (Manager) Check for the presence of a milestone for the release: - If there is a milestone, are all the issues for the milestone resolved? (other than this checklist). - [ ] (Manager) Inform Support/Marketing of impending release (and give estimated release dates). - - (SwEng) Prepare the sources for tarball generation. + - (SwEng) Prepare the sources for tarball generation: + - [ ] Check perflab to ensure there has been no unexplained drop in performance for the version being released. - [ ] Ensure that there are no outstanding merge requests in the private repository (subscription version only). - [ ] Update API files for libraries with new version information. - [ ] Change software version and library versions in configure.in (new major release only). - - [ ] Ensure Kyua and ATF files are correct. - [ ] Rebuild configure using autoconf on docs.isc.org. - [ ] Update CHANGES. - [ ] Update CHANGES.SE (subscription branch only). - [ ] Update "version". - [ ] Update "readme.md". - - [ ] Ensure the release notes are correct for this release (content, formatting, etc.). + - Check the release notes are correct: + - [ ] Compare content with merge requests for the release. + - [ ] Check formatting. - [ ] Build documentation on docs.isc.org. - [ ] Commit changes and make sure the gitlab-ci tests are passing. - [ ] Push the changes and tag ("alphatag" is an optional string such as "b1", "rc1" etc.). (```git tag -u -a -s -m "BIND 9.X.Y[alphatag]" v9_X_Y[alphatag]```) @@ -24,9 +26,19 @@ - [ ] (QA) Request the signature on the tarballs. - [ ] (QA) Check signatures on tarballs. - [ ] (QA) Tell Support to handle notification of release. - - [ ] (Support) Make tarballs and signatures available to download. - - [ ] (Manager) Update [https://wiki.isc.org/bin/view/Main/BindReleaseDates](BIND release dates page) when public announcement has been made. - - [ ] (Manager) Inform marketing of the release + - [ ] (Manager) Inform Marketing of the release + - [ ] (Manager) Update the internal [BIND release dates wiki page](https://wiki.isc.org/bin/view/Main/BindReleaseDates) when public announcement has been made. - [ ] (SwEng) Update DEB and RPM packages - [ ] (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`) + +## Support + - [ ] Make tarballs and signatures available to download. + - [ ] Write release email to bind9-announce. + - [ ] Write email to bind9-users (if a major release). + - [ ] Update tickets in case of waiting support customers. + +## Marketing + - [ ] Post short note to Twitter. + - [ ] Update [Wikipedia entry for BIND](http://en.wikipedia.org/wiki/BIND). + - [ ] Write blog article (if a major release).