mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-22 10:10:06 +00:00
Code Issues Releases Wiki Activity

Updates to BIND release checklist.

Browse Source
This commit is contained in:
Stephen Morris 2018-11-20 14:38:35 +00:00 committed by Ondřej Surý
parent 9145bec00d
commit 5c9c53e9e7
1 changed files with 19 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
.gitlab/issue_templates/release.md
View File

@ -1,19 +1,21 @@
## Release Checklist ## 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). - 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). - [ ] (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). - [ ] Ensure that there are no outstanding merge requests in the private repository (subscription version only).
- [ ] Update API files for libraries with new version information. - [ ] Update API files for libraries with new version information.
- [ ] Change software version and library versions in configure.in (new major release only). - [ ] 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. - [ ] Rebuild configure using autoconf on docs.isc.org.
- [ ] Update CHANGES. - [ ] Update CHANGES.
- [ ] Update CHANGES.SE (subscription branch only). - [ ] Update CHANGES.SE (subscription branch only).
- [ ] Update "version". - [ ] Update "version".
- [ ] Update "readme.md". - [ ] 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. - [ ] Build documentation on docs.isc.org.
- [ ] Commit changes and make sure the gitlab-ci tests are passing. - [ ] 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 <DEVELOPER_KEYID> -a -s -m "BIND 9.X.Y[alphatag]" v9_X_Y[alphatag]```) - [ ] Push the changes and tag ("alphatag" is an optional string such as "b1", "rc1" etc.). (```git tag -u <DEVELOPER_KEYID> -a -s -m "BIND 9.X.Y[alphatag]" v9_X_Y[alphatag]```)
@ -24,9 +26,19 @@
- [ ] (QA) Request the signature on the tarballs. - [ ] (QA) Request the signature on the tarballs.
- [ ] (QA) Check signatures on tarballs. - [ ] (QA) Check signatures on tarballs.
- [ ] (QA) Tell Support to handle notification of release. - [ ] (QA) Tell Support to handle notification of release.
- [ ] (Support) Make tarballs and signatures available to download. - [ ] (Manager) Inform Marketing of the release
- [ ] (Manager) Update [https://wiki.isc.org/bin/view/Main/BindReleaseDates](BIND release dates page) when public announcement has been made. - [ ] (Manager) Update the internal [BIND release dates wiki page](https://wiki.isc.org/bin/view/Main/BindReleaseDates) when public announcement has been made.
- [ ] (Manager) Inform marketing of the release
- [ ] (SwEng) Update DEB and RPM packages - [ ] (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`) - [ ] (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).