Georg Brandl ge...@python.org added the comment:
Applied in r72756.
--
resolution: - accepted
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5980
___
Daniel Diniz aja...@gmail.com added the comment:
We sure could have helpers for updating RFEs and bugs to correct
versions. They could be scripts for bulk updating and/or per-issue UI
shortcuts for Developers. I'll open a meta-tracker RFE for this.
Correcting user reports and requests is also
Terry J. Reedy tjre...@udel.edu added the comment:
Would these tasks, whereever documented, be entirely manual or partly
automated? I just fixed new feature request #5975 which originally
selected 2.5,2.6,3.0. It would be nice if the tracker automatically
rejected such invalid selections and
Terry J. Reedy tjre...@udel.edu added the comment:
I of course agree that these tasks should be listed somewhere, but have
no opinion on which PEP, if not both.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5980
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'
