launchpad development|
Size: 2834
Comment:
|
Size: 2716
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 6: | Line 6: |
| '''On Launchpad:''' https://blueprints.launchpad.net/launchpad/+spec/other-o-bug-lifecycle | '''On Launchpad:''' https://blueprints.launchpad.net/launchpad/+spec/other-o-bug-lifecycle; [[https://bugs.launchpad.net/launchpad-project/+bugs?field.tag=bug-lifecycle|bug-lifecycle]] |
| Line 70: | Line 70: |
| * https://bugs.launchpad.net/launchpad/+bug/777874 * https://bugs.launchpad.net/launchpad/+bug/777861 * https://bugs.launchpad.net/launchpad/+bug/777853 * https://bugs.launchpad.net/launchpad/+bug/777824 |
Bug lifecycle
Currently informational LEP on the lifecycle of bugs, especially with respect to statuses, assignment and milestones.
Contact: Jonathan Lange
On Launchpad: https://blueprints.launchpad.net/launchpad/+spec/other-o-bug-lifecycle; bug-lifecycle
Rationale
Ubuntu is driving hard toward being a much better quality distribution. As a part of this drive, Ubuntu is reviewing how it uses bugs and bug states in Launchpad.
Our aim here is to collect use cases for how bugs are used, identify points of friction and perhaps turn these into new requirements for how Launchpad should behave.
Note that these use cases should come from all of our stakeholders, not just Ubuntu.
Stakeholders
- Kate Stewart, Ubuntu Platform, 2011-04-20
- Allison Randal, Ubuntu Platform
User stories
Confirm fixes
As a developer
I want to see bugs that I think are fixed but need user testing
so that $BENEFIT
Waiting for replies
As a developer
I want to see a list of bugs with replies to my requests (e.g. clarification needed from reporter, testing needed, etc.)
so that I can quickly start to act on issues that I had previously been blocked on
Constraints and Requirements
Must
What MUST the new behaviour provide?
Nice to have
Must not
What MUST it not do?
Out of scope
Subfeatures
None.
Success
How will we know when we are done?
How will we measure how well we have done?
Thoughts?
Confusing states: Incomplete with(out) answer, Invalid/Opinion, Confirmed/Triaged and FixCommitted/FixReleased
In-app documentation of bug statuses would really help
- There is no way we can find a set of statuses that will match everyone's workflows, but there is value in a common set of canonical statuses. One way to solve it is to use a global simplified status (mpt's list) with a per-project configurable list of substatuses that will map the workflow of the project. Declined +opinion. In Progress +needstesting. That substatus would show in bug searches, be more than a simple tag. – ttx
- Looking at what kind of workflow-related tags people use is a good way of gaining insight as to use cases
