From 59e2a57906be123067d4a7ff926290571db15985 Mon Sep 17 00:00:00 2001 From: Robin Dunn Date: Wed, 7 Jun 2023 19:13:51 -0700 Subject: [PATCH] Updates for HOWTO-Release.txt --- buildbot/master.cfg | 2 +- packaging/HOWTO-Release.rst | 10 +++++++--- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/buildbot/master.cfg b/buildbot/master.cfg index 59a14d9d..a6d0a757 100644 --- a/buildbot/master.cfg +++ b/buildbot/master.cfg @@ -243,7 +243,7 @@ distBuilders = [ #'dist-osx-py36', 'dist-win32-py311', 'dist-win32-py312', #'dist-win64-py36', - 'dist-win64-py37', + #'dist-win64-py37', 'dist-win64-py38', 'dist-win64-py39', 'dist-win64-py310', diff --git a/packaging/HOWTO-Release.rst b/packaging/HOWTO-Release.rst index 6361f280..9026be68 100644 --- a/packaging/HOWTO-Release.rst +++ b/packaging/HOWTO-Release.rst @@ -80,15 +80,19 @@ HOWTO Release wxPython Phoenix 17. Tag the released revision in git, using a name like wxPython-4.0.0 (using the actual version number of course.) Push the tag to all remotes. -18. Bump the version numbers in buildtools/version.py appropriately for the +18. Make a release at GitHub. Copy the generated source file into the release, + and use a message that indicates the source archives created by GitHub are + not complete. + +19. Bump the version numbers in buildtools/version.py appropriately for the next anticipated release, so future snapshot builds will be recognized as pre-release development versions for the next official release, not the one just completed. -19. If making an announcement about this release, (I think it's okay not to +20. If making an announcement about this release, (I think it's okay not to for minor releases or smallish bug fixes,) send the text in packaging/ANNOUNCE.txt to the email addresses listed at the top of the file. -20. Add a news post to the wxPython site about the release. +21. Add a news post to the wxPython site about the release.