[Python-Dev] patch handling (was: Python 1.6 timing)

3 Feb 2000

      On Wed, 2 Feb 2000 bwarsaw@CNRI.Reston.VA.US wrote:
...
...
...
...
...
...
"Guido" == Guido van Rossum  writes:
...
    Guido> On the other hand, perhaps it would be better to deal with
    Guido> patches the same way as with bug reports -- the Jitterbug
    Guido> database isn't perfect, but it makes it possible to check
    Guido> regularly whether something has been dealt with or not,
    Guido> much better than a simple mailing list.  (There are already
    Guido> lieutenants scanning the bugs traffic, so that part doesn't
    Guido> change.)
Maybe then just use Jitterbug to collate patches.  That's what a lot
of my JPython users do.
Personally, I'm more comfortable knowing that I can email a patch (rather
than dropping it into a bug db), and that will get handled by a human. The
patch handlers could certainly use Jitterbug as arbitration, but I would
think the list itself would make that reasonably clear.

Note that "patches@python.org" could become THE place to submit patches.
Sure, Guido would get some patches still, but some of the load will drop
from his direct Inbox (yet he'd still get the patch as a subscriber). When
the patch handlers had a "final" patch, it would get sent straight to
Guido (with some "final" marker on it).

etc etc. I'm sure there is a lot discussion that can take place on the
exact mechanics. Until people will *volunteer*, I think the discussion of
mechanics can be postponed. No need for a peanut gallery here :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/