@@ -12,6 +12,8 @@ taking a lot of time to make a new one.
1212
1313#. Create a branch ``release-X.Y.Z `` with the version for the release.
1414
15+ * **maintenance releases **: from ``4.6-maintenance ``;
16+
1517 * **patch releases **: from the latest ``master ``;
1618
1719 * **minor releases **: from the latest ``features ``; then merge with the latest ``master ``;
@@ -24,7 +26,8 @@ taking a lot of time to make a new one.
2426
2527 This will generate a commit with all the changes ready for pushing.
2628
27- #. Open a PR for this branch targeting ``master ``.
29+ #. Open a PR for this branch targeting ``master `` (or ``4.6-maintenance `` for
30+ maintenance releases).
2831
2932#. After all tests pass and the PR has been approved, publish to PyPI by pushing the tag::
3033
@@ -33,7 +36,16 @@ taking a lot of time to make a new one.
3336
3437 Wait for the deploy to complete, then make sure it is `available on PyPI <https://pypi.org/project/pytest>`_.
3538
36- #. Merge the PR into ``master ``.
39+ #. Merge the PR.
40+
41+ #. If this is a maintenance release, cherry-pick the CHANGELOG / announce
42+ files to the ``master `` branch::
43+
44+ git fetch --all --prune
45+ git checkout origin/master -b cherry-pick-maintenance-release
46+ git cherry-pick --no-commit -m1 origin/4.6-maintenance
47+ git checkout origin/master -- changelog
48+ git commit # no arguments
3749
3850#. Send an email announcement with the contents from::
3951
0 commit comments