BIND issueshttps://gitlab.isc.org/isc-projects/bind9/-/issues2019-06-24T17:08:18Zhttps://gitlab.isc.org/isc-projects/bind9/-/issues/1054Release Checklist for 9.11.8, 9.12.4-P2, 9.14.3, 9.11.8-S12019-06-24T17:08:18ZStephen MorrisRelease Checklist for 9.11.8, 9.12.4-P2, 9.14.3, 9.11.8-S1## Release Checklist
- [x] (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).
- [x] (Manager) Inform Support/Mark...## Release Checklist
- [x] (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).
- [x] (Manager) Inform Support/Marketing of impending release (and give estimated release dates).
- (SwEng) Prepare the sources for tarball generation:
- [x] Check perflab to ensure there has been no unexplained drop in performance for the version being released.
- [x] Ensure that there are no outstanding merge requests in the private repository (subscription version only).
- [x] Update API files for libraries with new version information.
- [x] Change software version and library versions in configure.in (new major release only).
- [x] Rebuild configure using autoconf on docs.isc.org.
- [x] Update CHANGES.
- [x] Update CHANGES.SE (subscription branch only).
- [x] Update "version".
- [x] Update "readme.md".
- Check the release notes are correct:
- [x] Compare content with merge requests for the release.
- [x] Check formatting.
- [x] Build documentation on docs.isc.org.
- [x] Commit changes and make sure the gitlab-ci tests are passing.
- [x] 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]```)
- [x] If this is the first tag for a release (e.g. beta), create a release branch named `release_v9_X_Y` (this allows development to continue on the release branch whilst release engineering continues).
- [x] (QA) Run the "make release" Jenkins job to produce the tarballs and zips.
- [x] (QA) Sanity check the tarball and zips.
- [x] (QA) Sanity check the tarballs.
- [x] (QA) Request the signature on the tarballs.
- [x] (QA) Check signatures on tarballs.
- [x] (QA) Tell Support to handle notification of release.
- [x] (Manager) Inform Marketing of the release
- [x] (Manager) Update the internal [BIND release dates wiki page](https://wiki.isc.org/bin/view/Main/BindReleaseDates) when public announcement has been made.
- [x] (SwEng) Update DEB and RPM packages
- [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
- [x] Make tarballs and signatures available to download.
- [x] Write release email to bind9-announce.
- [x] Write email to bind9-users (if a major release).
- [x] Update tickets in case of waiting support customers.
## Marketing
- [x] Post short note to Twitter.
- [x] Update [Wikipedia entry for BIND](http://en.wikipedia.org/wiki/BIND).
- [x] Write blog article (if a major release).BIND 9.14.3Michael McNallyMichael McNally