Mercurial > evolve

view .gitlab/issue_templates/new-version.md @ 6546:30d0d3d92c8d stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
topic: properly process revbranchcache before sending it to peers (issue6841)
author Anton Shestakov <av6@dwimlabs.net>
date Fri, 25 Aug 2023 16:01:28 -0300
parents 8a7db813bd07
children ce450e90a0a5
line wrap: on
line source

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

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

Preparation

* [ ] merges with compatibility branches
* [ ] compatibility tests are happy
* [ ] update `testedwith` field
* [ ] make sure CHANGELOG is up-to-date
* [ ] [prepare an announcement for the list/website](https://mypads.framapad.org/p/evolution-announce-iswcp7qx)
* [ ] sanity check install and sdist targets of setup.py

Releasing

* [ ] add the current date to CHANGELOG
* [ ] update the `__version__` field of all relevant extensions
* [ ] create a new Debian entry
* [ ] tag the version
* [ ] move the `@` bookmark to the new tag
* [ ] push/publish the tag to the main repository
* [ ] upload the tarball to PyPI
* [ ] build .deb on Heptapod CI for the tagged commit
* [ ] add `.dev0` to the `__version__` field
* [ ] merge stable into default
* [ ] push the result to https://www.mercurial-scm.org/repo/evolve/
* [ ] 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/
* [ ] update #hg-evolve topic
* [ ] tweet about it