|
|
|
|
|
|
|
|
1. Change version in `config.mk`
|
|
|
1. Update `NEWS`
|
|
|
1. Make sure the tests are passing (automatic), and check respiff report (manual)
|
|
|
2. Check docker: https://hub.docker.com/r/cznic/knot-resolver/builds/
|
|
|
1. Check that generated files are up to date.
|
|
|
```
|
|
|
rm daemon/lua/kres-gen.lua etc/root.hints && make
|
|
|
```
|
|
|
1. Create a tag: `git -as 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. Documentation should regenerate automatically: check http://readthedocs.org/projects/knot-resolver/builds/
|
|
|
1. DNS should get updated automatically from tags: check `kdig et.knot-resolver.cz. TXT +short`
|
|
|
1. Create a tarball with `./scripts/make-archive.sh`
|
|
|
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 --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/):
|
|
|
```
|
|
|
curl -u name.surname -n --basic -T {,https://public.nic.cz/files/knot-resolver/}knot-resolver-x.y.z.tar.xz
|
|
|
```
|
|
|
1. Update the [Knot Resolver website](https://gitlab.labs.nic.cz/websites/knot-resolver.cz):
|
|
|
2. Create a branch in the web repo
|
|
|
2. Link to the sources in `content/pages/en/download.md`
|
|
|
2. Copy NEWS into a file in `content/news/en/` (+ simple header)
|
|
|
2. Packages
|
|
|
2. Preview web locally:
|
|
|
```
|
|
|
git submodule update --init --recursive
|
|
|
virtualenv .
|
|
|
source bin/activate
|
|
|
pip install -r requirements.txt
|
|
|
make
|
|
|
make serve &
|
|
|
xdg-open http://localhost:8000
|
|
|
```
|
|
|
2. Push the branch and merge it via web to master, leading to immediate deployment to knot-resolver.cz.
|
|
|
1. Write release e-mail to knot-dns-users mailing list.
|
|
|
1. Post some short note to [Twitter](https://twitter.com/KnotDNS)
|
|
|
1. Update all packages |