[RFC] Branches that fix bugs

[John Arbash Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jonathan Lange wrote:
> 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.
> 
> Are these clear? Would you change or remove any of these? Is there
> anything you would add?
> 
> jml
> 
> 

Oh and:

 - I want to be able to subscribe to commits that are addressing a
particular bug.
 - And filter my email based on what bug is being worked on

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpD81MACgkQJdeBCYSNAANEPQCfV6ModVeTS53O/ec6Q1k2EbF+
DAAAniNZ/UNk0ec7lC+pord9MWSlMuNH
=O6F7
-----END PGP SIGNATURE-----