Launchpad Bugs feature

Wouter van Heyst larstiq at larstiq.dyndns.org
Mon Apr 16 11:32:22 BST 2007


On Sat, Apr 14, 2007 at 07:46:48PM -0700, Robey Pointer wrote:
> 
> On 27 Mar 2007, at 18:54, Jonathan Lange wrote:
> 
> >Hello,
> >
> >I'm at the Bzr mini-sprint in Sydney working on a feature to allow
> >Launchpad to automatically close bugs based on information in Bazaar
> >revision properties.
> >
> >I'd love to get feedback on the proposed UI, the way revision
> >properties are used and where exactly this code should go.
> >
> >
> >Proposed UI:
> >
> >To indicate that a revision fixes a bug:
> >   * bzr commit --fixes=62789
> 
> 
> Just one comment in addition to the others already made:
> 
> The UI may not want to promise that the bug is fixed, just that the  
> commit "relates to" a specific bug.
> 
> We have a system like this where I work.  Commits can be associated  
> with a bug, and the commits show up in the bug report.  It is not  
> unheard of for a bug to require more than one commit.  Sometimes you  
> think you solved the bug but there was a deeper issue. :)
> 
> So I'd be opposed to using the word "--fixes" there.  Something like  
> "--bug" would be more honest.

Referencing a bug is certainly nice, but the Debian bts style of closing
bugs on the upload of a package is invaluable too.

Wouter van Heyst



More information about the bazaar mailing list