Changelog bug format

[Matt Zimmerman]

On Wed, Mar 15, 2006 at 10:05:28AM +0000, Daniel Silverstone wrote:
> 
> Option One: Re-use the malone email command interface to close bugs.
> Pros: Information/knowledge share, potential code share
> Cons: The malone email interface isn't ideal for changelogs. Could
> result in a too specific context in the changelog.

This would be useful as it provides a great deal of flexibility.  However,
it is too verbose for the most common operations, so an abbreviated format
is necessary.

> Example:
> Option Two: Simple modification of the Debian closes syntax
> Pros: Less change from an established format for changelogs already
> Cons: May be too easy to make a mistake and close a bug in the wrong
> tracker
> Example:
> foo (1.0) dapper; urgency=low
> 
>  * Did some stuff
>  * closes: lpbug #2001
> 
>  -- A Developer <dev at ubuntu.com> SomeDate
> Regexp: closes:\s*lpbug\s*#?\d+

I like this, especially in combination with option one.

> 
> Option Three: Instructions for launchpad
> Pros: Unlikely to be confused for another format, offers opportunity for
> extension later to things like marking specs as implemented.
> Cons: Slightly more verbiage than option two, not as neat and tidy.
> Introduces yet another language for talking about bugs etc.
> Example:
> foo (1.0) dapper; urgency=low
> 
>  * Did some stuff
>  * launchpad: close bug 2001
> 
>  -- A Developer <dev at ubuntu.com> SomeDate
> Regexp: ^[^A-Za-z0-9]*launchpad:\s*close(\s+bug)?\s+#?\d+

Still a bit too verbose.

-- 
 - mdz