From 0ce098edff7e6c1efb10782cea3fca67147a40e1 Mon Sep 17 00:00:00 2001 From: Sumana Harihareswara Date: Thu, 28 May 2020 17:37:11 -0400 Subject: [PATCH] Remove pypa-dev mention in release process Per https://groups.google.com/d/msg/pypa-dev/rUNsfIbruHM/LCEx-CB5AgAJ the pypa-dev Google Group is now decommissioned. Pointing to Discourse instead. Signed-off-by: Sumana Harihareswara --- RELEASING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index 0195b70a..752384fb 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -159,11 +159,11 @@ If in doubt, follow the basic instructions below. 3. Get credentials to co-maintain the pipenv project on PyPI.org -- **SPOF alert** 4. Set the version number to [a pre-release identifier](https://www.python.org/dev/peps/pep-0440/#pre-release-separators) 5. Package and upload pipenv [to PyPI](https://pypi.org/project/pipenv/#history) as a pre-release/alpha -6. Publicize on distutils-sig, pypa-dev, and the relevant GitHub issue(s) +6. Publicize on distutils-sig, [Discourse](https://discuss.python.org/c/packaging), and the relevant GitHub issue(s) a. write up diplomatic notification 7. Recruit manual testing ([example](https://pad.sfconservancy.org/p/help-test-pipenv-2020-03-26)) for workflows we don't account for 8. Wait a week, then update version number to a canonical release and re-release on PyPI.org -10. Publicize on lists, GitHub issues +10. Publicize on lists, Discourse, GitHub issues