Mercurial > evolve

view .gitlab/issue_templates/new-version.md @ 6202:fe8e88ea296d

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
evolve: use util.unlinkpath() via vfs Internally vfs.unlinkpath() does the path join and calls util.unlinkpath(). So the new form is equivalent, just shorter. This method exists in 4.8, so the new code shouldn't have any compatibility issues.
author Anton Shestakov <av6@dwimlabs.net>
date Sun, 13 Mar 2022 18:21:57 +0300
parents 74665d83fb3b
children 6b128ae8e2ad
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
* [ ] add `.dev` 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