Mercurial > evolve
view .gitlab/issue_templates/new-version.md @ 5395:366aaaae9a49
packaging: replace wget with curl in Build-Depends
At some point, evolve was using curl in some tests that check capabilities when
using HTTP. Then in 4e7da688a066 and 3ffa12edc05a it was replaced by wget for
Windows compatibility and debian/control was updated (in 783aa685c5d4).
Then, in e036dfc8cfcc the tests were switched back to using curl, but
debian/control was not updated until now.
| author | Anton Shestakov <av6@dwimlabs.net> |
|---|---|
| date | Sun, 05 Jul 2020 16:14:09 +0800 |
| parents | 7bcda49915e8 |
| children | 9e0f91cb5242 |
line wrap: on
line source
This is the actual check list for releasing evolve version X.Y.Z More details in the [README file](README#L179). 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