[python-committers] Three wishes for Mercurial-Roundup integration

Éric Araujo merwok at netwok.org
Fri Sep 2 18:53:30 CEST 2011


Le 31/08/2011 20:13, Georg Brandl a écrit :
>> 1) When a commit message references more than one bug (with text
>> matching #\d+), only the first gets a message for the changeset.  I
>> would like all referenced bugs to get a message.
> +1.  Just make sure that only issues that should be closed are closed
> (i.e. if the commit message is """Close #1234: better fix than proposed
> in #5678""", #1234 should be closed, and #5678 get a reference).

You, Nick and Terry are +1, Ezio -1.  I originally changed my mind and
agreed with Ezio after discussing it on IRC, on the basis that duplicate
bug should be sorted out in the tracker, but the majority here is in
favor.  I’ll wait a bit for other opinions.

>> 2) When a bug number (#\d+) is not in the first line of the commit
>> message, no message is sent.  Is there a reason for this or is it a bug?
>>  (Note: I’m not sure about this one, I may misremember.)

I did misremember, this works well.

>> 3) To let us track the backport of changesets from cpython/packaging to
>> distutils2, I would like the script to look at changesets in the
>> distutils2 repo and send messages to Roundup when a bug number is detected.
> Sure.  Should be a simple [hooks] entry.

Changing this requires admin access to hg.python.org, doesn’t it?  Can
Antoine or you make the changes (benchmarks, devguide, d2)?  Thanks.

Cheers


More information about the python-committers mailing list