New submission from Daniel Diniz <aja...@gmail.com>: 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? ---------- assignee: georg.brandl components: Documentation files: bugtracker.diff keywords: patch messages: 87508 nosy: ajaksu2, georg.brandl, loewis priority: low severity: normal status: open title: Add bug tracker tasks to PEP 101 type: feature request Added file: http://bugs.python.org/file13944/bugtracker.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue5980> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
