RetroSearch Browse

Wed Apr 2 09:12:05 CEST 2008 · https://mail.python.org/pipermail/python-dev/2008-April/078361.html

> > Yes, that's all I meant:  make it the committer's job
> > to merge or block as appropriate.  I just wasn't sure if
> > there was some reason that this would be difficult or
> > undesirable.
>
> Ah, yes. It is indeed difficult or undesirable, or was
> so in the past: Some committers don't care (didn't care)
> at all about 3k. They would have to setup sandboxes,
> learn what the nature of changes is, and invest some
> regular time into forward-porting.

Is this *really* the case still?  Who are these rogue committers? ;-)

I think holding a developer accountable for merging or blocking to py3k when they commit to trunk is a great idea.  Who better to pass judgement on such an activity than the person closest to it?

        Trent.

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2008-April/078361.html below:

[Python-Dev] No time for svn merge