Am 13.03.2010 17:51, schrieb Barry Warsaw: > I'm not necessarily saying these shouldn't go into 2.6.5, but this late in > the release cycle, every change needs to be justified. My preferred way of > doing so is by filing a release blocker issue stating and backing up the > requested change. We can then discuss any potential impact on release > testing and schedule. I'm fine with one issue if all these commits to the > release26-maint branch are for the same issue.
> Georg, please file that bug so we can formally decide whether or not to > include these in 2.6.5 final, and whether or not they require a 2.6.5 rc 3 > (which as you know I really don't want to do! ;) No need to file a new issue -- I've promoted 8111 to release blocker. I've added an explanation and a collective diff. No further RC is needed. Sorry for directly committing this, but I felt it was within my disgression as Documentation Expert and just fair -- after all PEP 101 states you have to get my approval during the release process, which I didn't see for these RCs :) cheers, Georg -- Thus spake the Lord: Thou shalt indent with four spaces. No more, no less. Four shall be the number of spaces thou shalt indent, and the number of thy indenting shall be four. Eight shalt thou not indent, nor either indent thou two, excepting that thou then proceed to four. Tabs are right out. _______________________________________________ python-committers mailing list [email protected] http://mail.python.org/mailman/listinfo/python-committers
