[RFC] Branches that fix bugs

Martin Pool mbp at sourcefrog.net
Fri Jun 26 01:10:01 BST 2009

2009/6/25 Jonathan Lange <jml at mumak.net>:
> The Launchpad developer discussion list recently started talking about
> how we link our Bazaar version control data to bugs.
> Right now, we have two or three ways of linking branches & revisions
> to bugs, none of which are used all the time. In particular, not many
> people are huge fans of the --fixes option, since it seems to require
> you to enter the bug fixing information at the wrong time.
> In the discussion, this list of desirable traits came up, and I
> thought it would make a good starting point for a discussion on the
> Bazaar list:
>  - I want to be able to link a branch to a bug offline
>  - I want to be able to say "this branch is intended to fix this bug"
> on branch creation
>  - I'd like to change my mind about bug branch links
>  - I'd like to distinguish between 'working on this bug' and 'fixes this bug'
>  - I'd like to say that a bug was fixed pretty much independently of
> when I commit.
>  - On mainline branches, I would like to know which revision introduced the fix.
>  - I want to see as much of this data as possible through the bzr
> command line (again offline), ideally as part of bzr log.

Those would be really useful.  I have some similar ones in
<http://doc.bazaar-vcs.org/devnotes/bzr-2009-ui-refresh.html> and you
can add a summary of this thread, or just a pointer to it, into that
branch if you wish.

Martin <http://launchpad.net/~mbp/>

More information about the bazaar mailing list