view .gitlab/issue_templates/new-version.md @ 5970:65d4e47d7f26

rewriteutil: use precheck from core if recent enough

This commit makes the evolve extension's `rewriteutil.precheck()`
simply delegate to the same function from Mercurial core, if that
function is deemed recent enough. The way I made that check is by
looking for `rewriteutil.find_new_divergence_from()`. That means that
there's a range of commits (ba6881c6::8125bcd2^) where the user would
see less detailed error messages if they are running with an hg
version from that range (there are no released versions in that
range).

As you can see in the tests, switching to core's version of the
function mostly affects error messages and exit codes.

This is the actual check list for releasing evolve version X.Y.Z

More details in the [README.rst file](README.rst#L199).

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 [e-mail]
* [ ] send the announcement by email to [e-mail]
* [ ] publish the announcement as a blog on https://octobus.net/blog/
* [ ] tweet about it