Merge lp:~jml/bzr/bug-branch-devnotes into lp:~bzr-core/bzr/devnotes

[Jonathan Lange]

[Jonathan Lange (jml)]

This branch separates the bug/branch linking stuff in the UI refresh out to a separate subsection of cases. It then adds notes from conversations on the Bazaar mailing list.

[Martin Pool (mbp)]

review: Approve

=== modified file 'bzr-2009-ui-refresh.txt'
--- bzr-2009-ui-refresh.txt	2009-07-03 01:50:21 +0000
+++ bzr-2009-ui-refresh.txt	2009-09-15 03:02:28 +0000
@@ -204,9 +204,6 @@
 I want to delete a branch from Launchpad (or another server) using just
 the bzr commandline client.
 
-As a Launchpad web user, I want to click from a fixed bug through to the
-branch and revision where it was originally fixed.
-
 As a code reviewer, I want to look through a patch series (like a loom) to
 see all the changes with history and in context.
 
@@ -227,10 +224,6 @@
 
 I'd like to run log (or vis, etc) across multiple branches.
 
-I'd like to create a branch intended to fix a particular bug and share
-this information with others, even before I've fixed the bug or made any
-commits on that branch.
-
 I'd like to quickly make a new branch, commit a drive-by fix (based off eg
 trunk?) then go back to where I was.
 
@@ -357,6 +350,55 @@
 branch.)
 
 
+Branches that fix bugs
+----------------------
+
+As a Launchpad web user, I want to click from a fixed bug through to the
+branch and revision where it was originally fixed.
+
+I'd like to create a branch intended to fix a particular bug and share
+this information with others, even before I've fixed the bug or made any
+commits on that branch.
+
+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.
+
+I also want to say, "it turns out this branch isn't going to fix that bug
+after all", independently of when I commit.
+
+On mainline branches, I would like to know which revision merged in 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.
+
+I want to be able to subscribe to commits that are addressing a particular
+bug.
+
+I want to filter my email based on what bug is being worked on
+
+I would like to easily know which branches do/do not contain a revision
+claiming to fix a particular bug.
+
+(perhaps) I want to see what revisions were committed that were intended to be
+part of this fix. (bzr log --related-to lp:33455)
+
+(perhaps) It would be good to mark a *group* of commits as fixing a bug, since
+I pretty much never implement the whole fix in a single commit. (Generally my
+--fixes commit is actually the one where I go update NEWS about having fixed
+the bug, which obviously has no actual code fix in itself.) -- jam
+
+I would like to be able to say which revision introduced a bug.
+
+
 Options
 *******