This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients mdk, ned.deily, rhettinger
Date 2020-11-02.00:51:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1604278279.28.0.616814835457.issue42238@roundup.psfhosted.org>
In-reply-to
Content
If it still does useful checks, we could just limit it to running by release managers during the release manufacturing process; it is already run then. It would still allow for problems to be caught and fixed by the RM prior to release tagging.  But I don't have a strong opinion about its overall usefulness. I recall it catching at least one problem in a release I was involved with and that was probably before we had the CI checks.
History
Date User Action Args
2020-11-02 00:51:19ned.deilysetrecipients: + ned.deily, rhettinger, mdk
2020-11-02 00:51:19ned.deilysetmessageid: <1604278279.28.0.616814835457.issue42238@roundup.psfhosted.org>
2020-11-02 00:51:19ned.deilylinkissue42238 messages
2020-11-02 00:51:19ned.deilycreate