It seems likely that we'll have to make a quick 2.6.4. Please, do not
commit anything to the 2.6-maint tree without checking with me first.
Thanks,
-Barry
PGP.sig
Description: This is a digitally signed message part
___
python-committers mailing l
On Oct 4, 2009, at 5:02 AM, Martin v. Löwis wrote:
It seems logging is broken in 2.6.3. Should we release
2.6.4 quickly?
http://bugs.python.org/issue7052
I believe both the logging fix and the distutils fix is in the tree
now, right? There are no other release blockers in the tracker.
Un
On Oct 4, 2009, at 7:38 AM, Antoine Pitrou wrote:
Perhaps we should leave a one-week delay between rc and final next
time,
so that this kind of late-minute issues have an opportunity to be
discovered ?
I'm skeptical it would have made a difference, and I seemed to have
misplaced the copy o
On Oct 4, 2009, at 2:06 PM, [email protected] wrote:
Antoine> Perhaps we should leave a one-week delay between rc and
final
Antoine> next time, so that this kind of late-minute issues have an
Antoine> opportunity to be discovered ?
Yeah, I was a little surprised the final release follow
> I'm skeptical it would have made a difference, and I seemed to have
> misplaced the copy of Guido's time machine keys that I had, but it's a
> worthwhile experiment anyway :).
>
> Shall we say 2.6.4rc1 tomorrow-ish and if no rc2 is necessary, a final
> release on Friday the 16th?
I'll likely be
Barry> But no release blockers in that set of bugs?
I've no idea. By the time I could submit the reports the final release was
out so I didn't even consider whether they would have been release blockers
or not.
Skip
___
python-committers mailing l
On Oct 5, 2009, at 5:00 PM, Martin v. Löwis wrote:
I'm skeptical it would have made a difference, and I seemed to have
misplaced the copy of Guido's time machine keys that I had, but
it's a
worthwhile experiment anyway :).
Shall we say 2.6.4rc1 tomorrow-ish and if no rc2 is necessary, a
fi
