Mercurial > evolve

view .gitlab/issue_templates/new-version.md @ 6135:ce7da767c7f6 stable

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
evolve: make _computeobsoleteset() return a frozenset Let's make sure that obsolete.getrevs(repo, b'obsolete') returns a frozenset to be compatible with Mercurial 6.1. This shouldn't produce any issues on older versions, because I doubt anything tries to modify a set of obsolete revisions by calling .add() or .remove() directly on it. See 27fe84a8dd60 and c7e675848027 in core.
author Anton Shestakov <av6@dwimlabs.net>
date Fri, 11 Feb 2022 18:10:51 +0300
parents df204c64faab
children 74665d83fb3b
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/
* [ ] tweet about it