Changelog bug format

[Tollef Fog Heen]

* Daniel Silverstone 

| 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.
| Example:
| foo (1.0) dapper; urgency=low
| 
|  * Did some stuff
|    bug 2001
|    affects /distros/ubuntu/dapper status fix-released

This is also impossible to reflow automatically.

| 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 prefer something like Mez suggested, personally I use Malone: #1234
The context is given from the changelog, so repeating that for each
bug is redundant.

-- 
Tollef Fog Heen                                                        ,''`.
UNIX is user friendly, it's just picky about who its friends are      : :' :
                                                                      `. `' 
                                                                        `-