view .gitlab/issue_templates/new-version.md @ 6847:f0a052aa924d

ci: run tests-py3 jobs on v2.0 images

We can't use v1.0 images because they still have Python 3.7.

Let's switch to using pip to install the extensions to avoid a
SetuptoolsDeprecationWarning about running setup.py directly. This also avoid
the warning about python_requires apparently.

The "running as root" warning cannot be simply avoided by using a different CI
image. We do have v2.1 images that default to ci-runner user, but no one
forbids people from running the test locally as a root user, one way or
another. Running pip as root shouldn't matter in this case, since it's not a
real system install, so this particular warning is always irrelevant.

This is the actual check list for releasing evolve version X.Y.Z

More details in the [README.rst file](README.rst#L219).

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
* [ ] build .deb on Heptapod CI for the tagged commit
* [ ] add `.dev0` to the `__version__` field
* [ ] merge stable into default
* [ ] push the result to https://repo.mercurial-scm.org/evolve/
* [ ] 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/
* [ ] update #hg-evolve topic
* [ ] tweet about it
* [ ] toot about it