Mercurial > evolve
view .gitlab/issue_templates/new-version.md @ 5884:21a8f0336f26 stable
next: treat targets that need evolution the same as regular targets
Unless --no-evolve is given.
In case when there's only one stable child that otherwise fits perfectly as a
hg next target, but there are also unstable children on the current topic and
we are allowed to evolve them, hg next should treat them as targets too and
give a prompt to select the revision to update to. With this patch it does.
| author | Anton Shestakov <av6@dwimlabs.net> |
|---|---|
| date | Thu, 22 Apr 2021 17:19:01 +0800 |
| parents | ca76e63e76dc |
| children | df204c64faab 7eb5b33868bc |
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#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 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