view .gitlab/issue_templates/new-version.md @ 5917:94aed9c7ce69 stable

next: refactor two if blocks into an if-elif block

We already checked the value of `needevolve and opts['evolve']` in the first if
block above. In the first one it need to be True, in the second it needs to be
False for the statements to execute. Since not(a or b) = not a and not b, we
can join the second if block to the first one with an elif while dropping the
explicit check.

For me, this works better, because we're doing the same thing in both of these
blocks (checking if working copy is dirty or not).

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 [e-mail]
* [ ] send the announcement by email to [e-mail]
* [ ] publish the announcement as a blog on https://octobus.net/blog/
* [ ] tweet about it