| 2010-04-15 16:41:07 |
MarcRandolph |
description |
Binary package hint: apport
Currently, the only way to determine that new crash (private) bugs have arrived is to visit the launchpad bug report for each individual Ubuntu package - no bug mail at all is generated. This might be fine if there were only a few packages to watch, but this does not scale to something like the Ubuntu project where there are thousands of packages. Many crashes are being ignored because projects are not closely watched. Even if I am only interested a small number of packages, I dare say it is pretty close to unworkable (having to remember to go visit the bug reports for each package).
I understand the desire to minimize bug spam, but could the flow be changed to the following to allow for at least one bug mail to be sent per non-duplicate bug?
1. retrace
2. dup check
3. if not a duplicate, notify those users subscribed to that package, and who are able to see private reports, with a status (if nothing else, just let them see the duplicate-check tag be removed). |
Binary package hint: apport
Currently, the only way to determine that new crash (private) bugs have arrived is to visit the launchpad bug report for each individual Ubuntu package - no bug mail at all is generated. This might be fine if there were only a few packages to watch, but this does not scale to something like the Ubuntu project where there are thousands of packages. Many crashes are being ignored or not handled in a timely manner because those packages are not visited. Even if I am only interested a small number of packages, I dare say it is pretty close to unworkable (having to remember to go visit the bug reports for each package).
I understand the desire to minimize bug spam, but could the flow be changed to the following to allow for at least one bug mail to be sent per non-duplicate bug?
1. retrace
2. dup check
3. if not a duplicate, notify those users subscribed to that package, and who are able to see private reports, with a status (if nothing else, just let them see the duplicate-check tag be removed).
|
|
