From 58f4db849e1880c88179a5f4fa3938cb8c8752bb Mon Sep 17 00:00:00 2001 From: meejah Date: Tue, 11 May 2021 11:53:11 -0600 Subject: [PATCH] update actual-release instructions --- docs/release-checklist.rst | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) diff --git a/docs/release-checklist.rst b/docs/release-checklist.rst index 75ab74bb1..953904f63 100644 --- a/docs/release-checklist.rst +++ b/docs/release-checklist.rst @@ -189,11 +189,16 @@ is appropriate. Once a release-candidate has marinated for some time then it can be made into a the actual release. -XXX Write this section when doing 1.15.0 actual release - -(In general, this means dropping the "rcX" part of the release and the -tag, uploading those artifacts, uploading to PyPI, ... ) +The actual release follows the same steps as above, with some differences: +- there is no "-rcX" on the end of release names +- the release is uploaded to PyPI (using Twine) +- the version is tagged in Git (ideally using "the tahoe release key" + but can be done with any of the authorized core developers' personal + key) +- the release-candidate branches must be merged back to master after + the release is official (e.g. causing newsfragments to be deleted on + master, etc) Announcing the Release