[python-committers] Blocking feature backports
Dirkjan Ochtman
dirkjan at ochtman.nl
Sun Dec 5 11:14:06 CET 2010
On Sat, Dec 4, 2010 at 16:25, Georg Brandl <g.brandl at gmx.net> wrote:
> As sad as it is, that's true. It's just unfair to developers and
> infrastructure providers to switch on such a short notice without a
> testing period.
Yeah, I'm very sorry. The last step in the conversion has proven
pretty annoying to get right. I need to separate release maintenance
branches from feature branches, and it turns out that due to the way
we use SVN, we also have a bunch of tag-related branches. I only found
out about the last part recently, and it looks fairly consistent, and
therefore hard to script.
Georg, I guess we should get together in IRC and see what makes sense
for a new schedule? Do we wait until after the 3.2 release now, or
just until after the holidays?
I'll keep on working on finding out what's happening with the tag branches.
Cheers,
Dirkjan
More information about the python-committers
mailing list