Home Original page

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

Terry Reedy tjreedy at udel.edu
Wed Aug 31 19:34:43 CEST 2011 
On 8/31/2011 10:39 AM, Éric Araujo wrote:

> 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 I would have expected this to be the case already. While there is 
something to be said for one issue -- one patch, there are legitimate 
exceptions. It is possible for two different surface level behavior bugs 
to be fixed by one underlying code patch. Also, I would prefer one patch 
for multiple typos fixed at the same time.
>
> 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.)

+1 I would have expected this also. While it is usually a good idea to 
put the issue number in the first line, I see this as a social issue 
rather than a technical issue. If an issue numbers on later lines is 
regarded as an error, then the technical fix would be to reject the 
patch with a message to the submitter. 'Errors should not pass silently'.

> 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.

+1 This would also help bug submitters who are using disutils2 on 
pre-3.3 releases to know that the fix is available to them also.

---
Terry Jan Reedy
More information about the python-committers mailing list