[python-committers] Unapproved commits after 2.6.5rc1
Jesse Noller
jnoller at gmail.com
Wed Mar 3 13:30:23 CET 2010
More information about the python-committers mailing list
Wed Mar 3 13:30:23 CET 2010
- Previous message: [python-committers] Unapproved commits after 2.6.5rc1
- Next message: [python-committers] Unapproved commits after 2.6.5rc1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 3, 2010, at 7:28 AM, Barry Warsaw <barry at python.org> wrote: > There have been a couple of commits to the Python 2.6 branch since the > 2.6.5rc1 tag. Since these were done by Florent and Victor, I just > wanted to > re-iterate that all substantive changes (i.e. anything other than > svnmerge > blocks) need to be approved while we're in release candidate mode. > > To get a change in between rc's and final releases, you should: > > * Create or elevate a bug to be a release blocker > * Attach your patch to the bug > * Discuss the change here or on python-dev > * Get approval for the change by me either via IRC or email > > The revisions in question are Victor's r78597 and Florent's r78621. > Since > these are not critical fixes, I am going to revert them. > > -Barry > They're both on this list, right?
- Previous message: [python-committers] Unapproved commits after 2.6.5rc1
- Next message: [python-committers] Unapproved commits after 2.6.5rc1
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list