Skip to content

Commit 8eefe4e

Browse files
authored
Merge pull request #7741 from bluetech/releasing-order
RELEASING: ~~first merge PR, then tag~~ clarify where to push the tag
2 parents b031a7c + 0274155 commit 8eefe4e

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

RELEASING.rst

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,8 @@ A bug-fix release is always done from a maintenance branch, so for example to re
2626

2727
Where ``5.1.x`` is the maintenance branch for the ``5.1`` series.
2828

29-
The automated workflow will publish a PR and notify it as a comment in the issue.
29+
The automated workflow will publish a PR for a branch ``release-5.1.2``
30+
and notify it as a comment in the issue.
3031

3132
Minor releases
3233
^^^^^^^^^^^^^^
@@ -41,7 +42,8 @@ Minor releases
4142

4243
@pytestbot please prepare release from 5.2.x
4344

44-
The automated workflow will publish a PR and notify it as a comment in the issue.
45+
The automated workflow will publish a PR for a branch ``release-5.2.0`` and
46+
notify it as a comment in the issue.
4547

4648
Major and release candidates
4749
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
@@ -60,7 +62,8 @@ Major and release candidates
6062

6163
@pytestbot please prepare release candidate from 6.0.x
6264

63-
The automated workflow will publish a PR and notify it as a comment in the issue.
65+
The automated workflow will publish a PR for a branch ``release-6.0.0`` and
66+
notify it as a comment in the issue.
6467

6568
At this point on, this follows the same workflow as other maintenance branches: bug-fixes are merged
6669
into ``master`` and ported back to the maintenance branch, even for release candidates.
@@ -101,9 +104,10 @@ Releasing
101104
Both automatic and manual processes described above follow the same steps from this point onward.
102105

103106
#. After all tests pass and the PR has been approved, tag the release commit
104-
in the ``MAJOR.MINOR.x`` branch and push it. This will publish to PyPI::
107+
in the ``release-MAJOR.MINOR.PATCH`` branch and push it. This will publish to PyPI::
105108

106-
git tag MAJOR.MINOR.PATCH
109+
git fetch --all
110+
git tag MAJOR.MINOR.PATCH upstream/release-MAJOR.MINOR.PATCH
107111
git push [email protected]:pytest-dev/pytest.git MAJOR.MINOR.PATCH
108112

109113
Wait for the deploy to complete, then make sure it is `available on PyPI <https://pypi.org/project/pytest>`_.

0 commit comments

Comments
 (0)