BugWorkflow
|
⇤ ← Revision 1 as of 2009-06-05 14:48:18
Size: 2567
Comment:
|
Size: 4989
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| === Goal === Maximize the amount of bug fixing that occurs per unit time invested in bugs management by desktop team engineers. |
|
| Line 10: | Line 12: |
| This should provide an overview of the issue/functionality/change proposed here. Focus here on what will actually be DONE, summarising that so that other people don't have to read the whole spec. See also CategorySpec for examples. | === Rationale === The current situation is: * Many desktop team engineers are swamped with bug reports. That is, there are more bug reports in their areas of responsibility than they can reasonably address. * The desktop team has a history of addressing each and every bug report. * Bug reports are a vital source of feedback regarding the quality of the product. * Users have an expectation that a bug report will result in a timely fix, and may even expect support via their bug report. |
| Line 12: | Line 19: |
| == Release Note == | The goal state is: * Desktop team engineers can meet their obligations regarding bug triaging. * Desktop engineers can spend more time fixing bugs when appropriate. * End users have appropriate expectations regarding the impact of their bug reports. |
| Line 14: | Line 24: |
| This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.) It is mandatory. == Rationale == This should cover the _why_: why is this change being proposed, what justifies it, where we see this justified. |
=== Approach === A multi-pronged approach is being used to make progress towards this goal state: 1. The launchpad team is changing launchpad so that it helps users use ubuntu-bugs to report bugs. This should result in fewer but better quality bug reports. 1. pitti is enhancing ubuntu-bugs to be "symptom based" (see ). This should result in even better bug reports. 1. Work with the launchpad team to add verbiage to launchpad that could help set the users' expectations regarding bug reports. 1. The launchpad team will add an "expired" state to older bugs, reducing the noise in the system. 1. The desktop team engineers will limit bugs assigned to them to bugs that are targeted to be fixed in the current cycle. 1. Craft a tool that dramatically speeds up the bug triaging process. 1. Craft a tool that "watches" for bugs in new uploads, allowing engineers to respond to regressions more quickly. |
| Line 23: | Line 35: |
| === End User === A user encounters a bug in program Foo. Based on previous experience they go to launchpad.net to log the bug. When click the link to add a bug, they are shown instructions to use ubuntu-bugs. They run ubuntu-bugs which gathers data relevant to their symptoms and logs the bug for them. When the bug is logged they see a message telling them that the bug will be triaged, but may not be fixed, and also tells them where to go for support. === Triaging Tool === seb128 starts work in the morning. He fires up an app that chugs away on launchpad loading bugs into a list in the areas of GNOME that he works on. He gets some coffee and works on email. When the list is finished loading, he is able to look over the list and select bugs in batches. He can click buttons to set the bugs into different states, such as upstream, won't fix, etc.... When he is done, he knows that he has triaged all the new bugs in his area. === Doing an Upload === asac uploads a firefox security fix. An hour later he starts getting bug mails about a regression some users experience. The mails are marked as being related to his recent upload (reason=upload watch). He triages the bugs. He gets similar bug reports for the next 48 hours. After 48 hours, the emails stop coming related to the upload, though bug mails are sent in the normal fashion. |
Launchpad Entry: foo
Created:
Contributors:
Packages affected:
Summary
Goal
Maximize the amount of bug fixing that occurs per unit time invested in bugs management by desktop team engineers.
Rationale
The current situation is:
- Many desktop team engineers are swamped with bug reports. That is, there are more bug reports in their areas of responsibility than they can reasonably address.
- The desktop team has a history of addressing each and every bug report.
- Bug reports are a vital source of feedback regarding the quality of the product.
- Users have an expectation that a bug report will result in a timely fix, and may even expect support via their bug report.
The goal state is:
- Desktop team engineers can meet their obligations regarding bug triaging.
- Desktop engineers can spend more time fixing bugs when appropriate.
- End users have appropriate expectations regarding the impact of their bug reports.
Approach
A multi-pronged approach is being used to make progress towards this goal state:
- The launchpad team is changing launchpad so that it helps users use ubuntu-bugs to report bugs. This should result in fewer but better quality bug reports.
- pitti is enhancing ubuntu-bugs to be "symptom based" (see ). This should result in even better bug reports.
- Work with the launchpad team to add verbiage to launchpad that could help set the users' expectations regarding bug reports.
- The launchpad team will add an "expired" state to older bugs, reducing the noise in the system.
- The desktop team engineers will limit bugs assigned to them to bugs that are targeted to be fixed in the current cycle.
- Craft a tool that dramatically speeds up the bug triaging process.
- Craft a tool that "watches" for bugs in new uploads, allowing engineers to respond to regressions more quickly.
User stories
End User
A user encounters a bug in program Foo. Based on previous experience they go to launchpad.net to log the bug. When click the link to add a bug, they are shown instructions to use ubuntu-bugs. They run ubuntu-bugs which gathers data relevant to their symptoms and logs the bug for them. When the bug is logged they see a message telling them that the bug will be triaged, but may not be fixed, and also tells them where to go for support.
Triaging Tool
seb128 starts work in the morning. He fires up an app that chugs away on launchpad loading bugs into a list in the areas of GNOME that he works on. He gets some coffee and works on email. When the list is finished loading, he is able to look over the list and select bugs in batches. He can click buttons to set the bugs into different states, such as upstream, won't fix, etc.... When he is done, he knows that he has triaged all the new bugs in his area.
Doing an Upload
asac uploads a firefox security fix. An hour later he starts getting bug mails about a regression some users experience. The mails are marked as being related to his recent upload (reason=upload watch). He triages the bugs. He gets similar bug reports for the next 48 hours. After 48 hours, the emails stop coming related to the upload, though bug mails are sent in the normal fashion.
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
Include:
- data migration, if any
- redirects from old URLs to new ones, if any
- how users will be pointed to the new way of doing things, if necessary.
Test/Demo Plan
It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
DesktopTeam/Specs/Karmic/BugWorkflow (last edited 2009-06-17 16:08:12 by 97-126-113-52)