p53209761
/
test_ok2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

RELEASING: start new dev cycle by tagging MAJOR.{MINOR+1}.0.dev0 in master 

This is needed so setuptools-scm in master shows an accurate version.
In particular, higher than the stable branch.
This commit is contained in:
Ran Benita 2020-10-17 19:08:48 +03:00
parent 701ff1f5a1
commit f6b682ad49
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
RELEASING.rst
View File

@ -122,6 +122,14 @@ Both automatic and manual processes described above follow the same steps from t
#. Open a PR for ``cherry-pick-release`` and merge it once CI passes. No need to wait for approvals if there were no conflicts on the previous step.
#. For major and minor releases, tag the release cherry-pick merge commit in master with
a dev tag for the next feature release::
git checkout master
git pull
git tag MAJOR.{MINOR+1}.0.dev0
git push git@github.com:pytest-dev/pytest.git MAJOR.{MINOR+1}.0.dev0
#. Send an email announcement with the contents from::
doc/en/announce/release-<VERSION>.rst