head-checking: also test single head enforcement with topic
They are an important part of why we want this.
This is the actual check list for releasing evolve version X.Y.Z
More details in the [README file](README#L179).
Preparation
* [ ] merges with compatibility branches
* [ ] compatibility tests are happy
* [ ] update `testedwith` field
* [ ] make sure the changelog is up to data
* [ ] [prepare an announcement for the list/website](https://mypads.framapad.org/mypads/?/mypads/group/octobus-public-5d3rw470w/pad/view/evolution-announce-iswcp7qx)
* [ ] sanity check install and sdist targets of setup.py
Releasing
* [ ] add the current date to the changelog
* [ ] update the `__version__` field of all relevant extensions
* [ ] create a new Debian entry
* [ ] tag the version
* [ ] move the `@` bookmark on the new tag
* [ ] push/publish the tag to the main repository
* [ ] upload the tarball to PyPI
* [ ] add `.dev` to the `__version__` field
* [ ] merge stable into default
* [ ] push the result on the main repo
* [ ] send the announcement by email to evolve-testers@mercurial-scm.org
* [ ] send the announcement by email to mercurial@mercurial-scm.org
* [ ] publish the announcement as a blog on https://octobus.net/blog/
* [ ] tweet about it