Skip to content

GitLab

Closed
Created by Stephen Morris@stephen56 of 77 tasks completed56/77 tasks

Release 9.11.6, 9.12.4,9.14.0rc1

Checklist

  • (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).

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (Manager) Inform Support/Marketing of impending release (and give estimated release dates).

    • Complete.

  • (SwEng) Prepare the sources for tarball generation:

    • Check perflab to ensure there has been no unexplained drop in performance for the version being released.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Ensure that there are no outstanding merge requests in the private repository.
      • N/A
    • Update API files for libraries with new version information.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Change software version and library versions in configure.in (new major release only).
      • N/A
    • Rebuild configure using autoconf on docs.isc.org.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Update CHANGES.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Update CHANGES.SE (subscription branch only).
      • N/A
    • Update "version".
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Update "README.md".
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Check the release notes are correct:
      • Compare content with merge requests for the release.
        • 9.11.6
        • 9.12.4
        • 9.14.0rc1
      • Check formatting.
        • 9.11.6
        • 9.12.4
        • 9.14.0rc1
    • Build documentation on docs.isc.org.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Merge and push changes.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Confirm the gitlab-ci tests are passing.
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • Push the changes and tag ("alphatag" is an optional string such as "b1", "" etc.). (git tag -u <DEVELOPER_KEYID> -a -s -m "BIND 9.X.Y[alphatag]" v9_X_Y[alphatag])
      • 9.11.6
      • 9.12.4
      • 9.14.0rc1
    • 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).
      • N/A

  • (QA) Run the "make release" Jenkins job to produce the tarballs and zips.

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (QA) Sanity check the tarballs. (https://wiki.isc.org/bin/view/QA/BindQaResults_9_11_6)

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (QA) If a security release, check that the issue in question has been resolved.

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (QA) Request the signature on the tarballs.

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (QA) Check signatures on tarballs.

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (QA) Tell Support to handle notification of release.

    • Done.

  • (Manager) Inform Marketing of the release

    • Done.

  • (Manager) Update the internal BIND release dates wiki page when public announcement has been made.

    • 9.11.6
    • 9.12.4

  • (SwEng) Update DEB packages

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (SwEng) Update RPM packages

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

  • (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)

    • 9.11.6
    • 9.12.4
    • 9.14.0rc1

Support

  • Make tarballs and signatures available to download.
    • 9.11.6
    • 9.12.4
    • 9.14.0rc1
  • Write release email to bind9-announce.
    • 9.11.6
    • 9.12.4
    • 9.14.0rc1
  • Write email to bind9-users (if a major release).
    • N/A
  • Update tickets in case of waiting support customers.
    • Complete.

Marketing

  • Post short note to Twitter.
    • Complete.
  • Update Wikipedia entry for BIND.
    • Complete.
  • Write blog article (if a major release).
    • N/A
Edited by Stephen Morris