| 2008-02-28 14:29:48 |
Andrew Clausen |
bug |
|
|
added bug |
| 2008-02-28 16:23:24 |
Diogo Matsubara |
malone: status |
New |
Invalid |
|
| 2008-02-29 04:54:34 |
Matthew Paul Thomas |
malone: status |
Invalid |
Confirmed |
|
| 2008-02-29 04:54:34 |
Matthew Paul Thomas |
malone: importance |
Undecided |
High |
|
| 2008-02-29 04:57:06 |
Matthew Paul Thomas |
description |
I think Launchpad's criteria for bug expiry are problematic. From what I can tell, the goal is to ignore bugs for which the person who reported it doesn't give enough information to reproduce it. But if a bug report has been marked as incomplete, then it will expire in 60 days EVEN IF THE USER FOLLOWS UP WITH MORE INFORMATION. I don't think it's helpful for developers to kill of bugs that developers haven't had time to look at yet.
An example of a bug that is scheduled to expire is:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/176735 |
At the time of writing, bug 176735 begins with an alert saying "This bug report will be marked for expiration in 59 days if no further activity occurs", even though the reporter has commented twice since the bug report was marked Incomplete.
|
|
| 2008-02-29 04:57:06 |
Matthew Paul Thomas |
title |
bug expiry: inactive users vs inactive developers |
Incomplete report "will be marked for expiration" even if reporter has followed up |
|
| 2008-02-29 05:24:16 |
Matthew Paul Thomas |
description |
At the time of writing, bug 176735 begins with an alert saying "This bug report will be marked for expiration in 59 days if no further activity occurs", even though the reporter has commented twice since the bug report was marked Incomplete.
|
1. Report a bug (e.g. at <https://bugs.staging.launchpad.net/>).
2. Have someone else mark the report as Incomplete.
3. Comment on the bug report.
What happens: The bug report says "This bug report will be marked for expiration in 59 days if no further activity occurs."
What should happen: If that's true, it shouldn't be true, because bug reports where the reporter has followed up are supposed to be excluded from expiration. And if it's not true, Launchpad shouldn't say it is.
This bug occurred in bug 176735 and bug 53851.
|
|
| 2011-12-19 10:24:16 |
Robert Collins |
launchpad: importance |
High |
Low |
|
| 2014-01-07 12:28:52 |
Matthew Paul Thomas |
description |
1. Report a bug (e.g. at <https://bugs.staging.launchpad.net/>).
2. Have someone else mark the report as Incomplete.
3. Comment on the bug report.
What happens: The bug report says "This bug report will be marked for expiration in 59 days if no further activity occurs."
What should happen: If that's true, it shouldn't be true, because bug reports where the reporter has followed up are supposed to be excluded from expiration. And if it's not true, Launchpad shouldn't say it is.
This bug occurred in bug 176735 and bug 53851.
|
1. Report a bug (e.g. at <https://bugs.staging.launchpad.net/>).
2. Have someone else mark the report as Incomplete.
3. Comment on the bug report.
What happens: The bug report says "This bug report will be marked for expiration in 59 days if no further activity occurs."
What should happen: If that's true, it shouldn't be true, because bug reports where the reporter has followed up are supposed to be excluded from expiration. And if it's not true, Launchpad shouldn't say it is.
This bug occurred, for example, in bug 53851, bug 176735, and bug 1219942.
This is a subset of bug 290101. |
|
