2006-05-09 22:09:18 |
Robert Collins |
bug |
|
|
added bug |
2006-05-09 22:09:33 |
Robert Collins |
launchpad: severity |
Normal |
Wishlist |
|
2006-05-09 22:09:33 |
Robert Collins |
launchpad: statusexplanation |
|
|
|
2006-05-10 04:05:06 |
Matthew Paul Thomas |
marked as duplicate |
|
3383 |
|
2006-05-10 09:14:55 |
Matthew Paul Thomas |
removed duplicate marker |
3383 |
|
|
2006-08-30 13:57:35 |
Brad Bollenbach |
malone: status |
Unconfirmed |
Confirmed |
|
2006-08-30 13:57:35 |
Brad Bollenbach |
malone: statusexplanation |
|
I think the use case of wanting to explain good bug filing practices via a wiki page or text field in LP is a good idea, so I'll mark this confirmed, at least, with more thought required later about how to address the underlying issues.
For example, I've noticed that many of the bug reports linked in the Ubiquity known issues doc would score very highly with "bug heat", a score based on things like number of subscribers, number of dupes, and other signs of a bug's gravitational pull.
The work I'm doing on a guided bug workflow will show, at least initially, only the "most common" (i.e. most duped) bugs, because a heat query could be too expensive for our current db model, since this is not yet a score cached in the Bug table.
So this solution could help address the "Known Issues" use case when reporting a bug (except for those who would actively avoid the guided bug workflow. :P) |
|
2006-12-12 11:24:07 |
Steve Alexander |
malone: importance |
Wishlist |
High |
|
2006-12-12 11:24:07 |
Steve Alexander |
malone: statusexplanation |
I think the use case of wanting to explain good bug filing practices via a wiki page or text field in LP is a good idea, so I'll mark this confirmed, at least, with more thought required later about how to address the underlying issues.
For example, I've noticed that many of the bug reports linked in the Ubiquity known issues doc would score very highly with "bug heat", a score based on things like number of subscribers, number of dupes, and other signs of a bug's gravitational pull.
The work I'm doing on a guided bug workflow will show, at least initially, only the "most common" (i.e. most duped) bugs, because a heat query could be too expensive for our current db model, since this is not yet a score cached in the Bug table.
So this solution could help address the "Known Issues" use case when reporting a bug (except for those who would actively avoid the guided bug workflow. :P) |
|
|
2007-01-22 11:15:23 |
Björn Tillenius |
malone: assignee |
|
bjornt |
|
2007-02-12 02:22:01 |
Matthew Paul Thomas |
description |
Some packages have specific instructions the maintainers would like to have followed when filing bugs. When a source package is selected as the target for a new bug, it would be very helpful if a link specific to the package [or perhaps some wiki style text] was shown with the guidelines the submitter should follow. The specific case in point prompting this is the kernel bug team: they have a wiki document at https://wiki.ubuntu.com/DebuggingKernelProblems (which is about to be made more useful) that documents the information needed for a useful bug report *on that package*. |
Some products and packages have specific instructions the maintainers would like to have followed when filing bugs. It would be very helpful if guidelines specific to the product or package [or perhaps some wiki style text] were presented during the bug-reporting process.
For example, the kernel bug team have a wiki document at <https://wiki.ubuntu.com/DebuggingKernelProblems> that documents the information needed for a useful bug report *on that package*. |
|
2007-02-12 02:22:01 |
Matthew Paul Thomas |
title |
Should be able to link to a wiki page with bug filing guidelines per source package. |
Allow product-/package-specific bug-reporting guidelines |
|
2007-04-19 08:46:24 |
Björn Tillenius |
malone: assignee |
bjornt |
allenap |
|
2007-04-19 08:46:24 |
Björn Tillenius |
malone: statusexplanation |
|
Yeah, I think it Gavin could take this one. |
|
2007-10-23 14:30:10 |
Gavin Panella |
malone: milestone |
|
1.1.12 |
|
2007-10-30 13:59:36 |
Björn Tillenius |
description |
Some products and packages have specific instructions the maintainers would like to have followed when filing bugs. It would be very helpful if guidelines specific to the product or package [or perhaps some wiki style text] were presented during the bug-reporting process.
For example, the kernel bug team have a wiki document at <https://wiki.ubuntu.com/DebuggingKernelProblems> that documents the information needed for a useful bug report *on that package*. |
Some products and packages have specific instructions the maintainers would like to have followed when filing bugs. It would be very helpful if guidelines specific to the product or package [or perhaps some wiki style text] were presented during the bug-reporting process.
For example, the kernel bug team have a wiki document at <https://wiki.ubuntu.com/DebuggingKernelProblems> that documents the information needed for a useful bug report *on that package*.
Initially the guidelines will be per project and distribution only. Doing to same for packages will be done later. |
|
2007-10-30 13:59:36 |
Björn Tillenius |
title |
Allow product-/package-specific bug-reporting guidelines |
Allow product-/distribution-specific bug-reporting guidelines |
|
2007-11-15 11:00:43 |
Gavin Panella |
malone: status |
Confirmed |
Triaged |
|
2007-11-30 11:32:57 |
Gavin Panella |
malone: status |
Triaged |
In Progress |
|
2007-12-06 12:07:45 |
Matthew Paul Thomas |
description |
Some products and packages have specific instructions the maintainers would like to have followed when filing bugs. It would be very helpful if guidelines specific to the product or package [or perhaps some wiki style text] were presented during the bug-reporting process.
For example, the kernel bug team have a wiki document at <https://wiki.ubuntu.com/DebuggingKernelProblems> that documents the information needed for a useful bug report *on that package*.
Initially the guidelines will be per project and distribution only. Doing to same for packages will be done later. |
Some projects and packages have specific instructions the maintainers would like to have followed when filing bugs. It would be very helpful if guidelines specific to the project or package [or perhaps some wiki style text] were presented during the bug-reporting process.
For example, the kernel bug team have a wiki document at <https://wiki.ubuntu.com/DebuggingKernelProblems> that documents the information needed for a useful bug report *on that package*.
Initially the guidelines will be per project and distribution only. Doing to same for packages will be done later. |
|
2007-12-06 12:07:45 |
Matthew Paul Thomas |
title |
Allow product-/distribution-specific bug-reporting guidelines |
Allow project-/package-specific bug-reporting guidelines |
|
2007-12-12 22:34:47 |
Gavin Panella |
malone: status |
In Progress |
Fix Committed |
|
2007-12-21 10:35:17 |
Gavin Panella |
malone: status |
Fix Committed |
Fix Released |
|
2008-01-05 19:42:05 |
Matthew Paul Thomas |
malone: status |
Fix Released |
Confirmed |
|
2008-01-05 19:42:05 |
Matthew Paul Thomas |
malone: milestone |
1.1.12 |
|
|
2008-11-14 17:41:41 |
Gavin Panella |
malone: status |
Confirmed |
Triaged |
|
2008-11-14 17:41:41 |
Gavin Panella |
malone: statusexplanation |
Reopening based on the last four comments. The initial use case reported in this bug was guidelines specific to the kernel package, and that has not been implemented. |
|
|
2008-11-18 17:08:40 |
Gavin Panella |
malone: status |
Triaged |
Fix Committed |
|
2008-11-18 17:08:40 |
Gavin Panella |
malone: statusexplanation |
|
Package-specific guidelines landed in r7300. |
|
2008-12-01 18:40:05 |
Brian Murray |
malone: status |
Fix Committed |
Fix Released |
|
2008-12-01 18:40:05 |
Brian Murray |
malone: statusexplanation |
Package-specific guidelines landed in r7300. |
Package specific bug-reporting guidelines have landed on the production server now so I am setting this bug's status to Fix Released. |
|