Mercurial > evolve
view .gitlab/issue_templates/new-version.md @ 6130:cd07d6bd4e2a
cmdrewrite: a new `hg fixup` command
This new command can be used to amend specific revisions with working copy
changes.
Implementation-wise what it basically does is:
1) commit working directory changes
2) relocate the new commit onto the target commit
3) fold them into one.
After the run, the working directory parent will be the obsoleted changeset
created in step 1 and descendants of the target will become orphans.
| author | Sushil khanchi <sushilkhanchi97@gmail.com> |
|---|---|
| date | Wed, 03 Nov 2021 22:59:17 +0530 |
| parents | 7eb5b33868bc |
| children |
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/ * [ ] update #hg-evolve topic * [ ] tweet about it