|
|
# Release Checklist
|
|
|
|
|
|
1. Change version in `config.mk`
|
|
|
1. Update `NEWS`
|
|
|
1. Make sure the tests are passing
|
|
|
1. Create a tag (name `vX.Y.Z[-alphatag]`, content `Knot Resolver X.Y.Z[-alphatag]`, signed with a developer's GPG key)
|
|
|
1. Push the changes and tag
|
|
|
1. Create a tarball with: `git archive --output=../knot-resolver-X.Y.Z.tar.xz --prefix=knot-resolver-X.Y.Z/ -- vX.Y.Z`
|
|
|
1. Update the https://knot-resolver.readthedocs.io/ documentation
|
|
|
1. Upload the tarball:
|
|
|
2. Use [sign-and-upload-knot-release`](https://gitlab.labs.nic.cz/labs/knot/snippets/63) script or following:
|
|
|
3. Generate signature using the Knot DNS signing key (`gpg --detach-sign --armor --default-key 0xACE24DA9EE37A832 --digest-algo SHA512 knot-resolver-x.y.z.tar.xz`).
|
|
|
3. Generate checksum file (`sha256sum knot-resolver-x.y.z.tar.xz > knot-resolver-x.y.z.tar.xz.sha256`).
|
|
|
3. Upload the tarball, signature, and checksum to [secure.nic.cz](https://secure.nic.cz/files/knot-resolver/).
|
|
|
1. Update the [Knot DNS website](http://www.knot-resolver.cz/)
|
|
|
2. Link to the sources
|
|
|
2. Information about the version
|
|
|
2. Known problems
|
|
|
2. Packages
|
|
|
1. Write release e-mail to knot-dns-users mailing list.
|
|
|
1. Post some short note to [Twitter](https://twitter.com/KnotDNS)
|
|
|
1. Update http://en.wikipedia.org/wiki/Knot_Resolver
|
|
|
1. Update all packages |