> > 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.
_______________________________________________
Python-Dev mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
