launchpad development
Bug-branch linking
Automatically linking bugs to branches and vice versa.
Contact: Jonathan Lange
On Launchpad: bug-branch-links
Link this from LEP
Rationale
Why are we doing this now?
What value does this give our users? Which users?
Stakeholders
Who really cares about this feature? When did you last talk to them?
User stories
As a software developer
I want to say "I am now trying to fix this bug" using my VCS tool
so that others can see what I'm doing, help me if they want to, and not duplicate my work by accident
As a software developer
I want to change my mind about the bug that I'm fixing
so that I don't stall unnecessarily on getting the bug number right in the first place
As a software developer
I want to say "I have given up trying fix this bug" using my VCS tool
so that others can have a go trying to fix it
As a software developer
I want to say "this bug is now fixed" using my VCS tool
so that we have a record of what it took to fix the bug
As a software developer
I want to say "this bug is now fixed" using my VCS tool without committing
so that I don't have to predict the future
As a power user of some software
I want to be able to look at a fixed bug in Launchpad and quickly go to the trunk revision where it was fixed
so that I can see what it took to fix the bug
Constraints and Requirements
Must
- All VCS-driven behaviour must work when offline, and sync to Launchpad when online
- Distinguish between 'working on this bug' and 'fixes this bug'
- Be able to say that a bug was fixed pretty much independently of when you commit
Nice to have
Some way to mark a group of revisions as fixing a bug
- See which revisions were committed that were intended to be part of this fix. (bzr log --related-to lp:33455)
Must not
Out of scope
- Any version control system other than Bazaar
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
Put everything else here. Better out than in.
