➜

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 ajaksu2
Recipients ajaksu2, georg.brandl, loewis
Date 2009-05-09.19:24:22
SpamBayes Score 6.514783e-08
Marked as misclassified No
Message-id <1241897065.28.0.181996092756.issue5980@psf.upfronthosting.co.za>
In-reply-to
Content 
This patch would add the following bug tracker tasks to PEP 101 (Doing
Python Releases 101):
 - Add version X.Y+1 as when version X.Y enters alpha.

 - Change non-doc RFEs to version X.Y+1 when version X.Y enters beta.

 - Update 'behavior' issues from versions that your release make
   unsupported to the next supported version.

 - Review open issues, as this might find lurking showstopper bugs,
   besides reminding people to fix the easy ones they forgot about.

These are the changes mentioned in
http://psf.upfronthosting.co.za/roundup/meta/issue283

However, I'm tempted to update PEP 3 (Guidelines for Handling Bug
Reports) instead, adding these (and the blocker <-> deferred flips) as
tracker janitors' tasks.

What do you think?
History
Date User Action Args
2009-05-09 19:24:25ajaksu2setrecipients: + ajaksu2, loewis, georg.brandl
2009-05-09 19:24:25ajaksu2setmessageid: <1241897065.28.0.181996092756.issue5980@psf.upfronthosting.co.za>
2009-05-09 19:24:23ajaksu2linkissue5980 messages
2009-05-09 19:24:23ajaksu2create