Le 02/04/2015 11:32, Thierry Carrez a écrit :
Sean Dague wrote:
I just spent a chunk of the morning purging out some really old
Incomplete bugs because about 9 months ago we disabled the auto
expiration bit in launchpad -
https://bugs.launchpad.net/nova/+configure-bugtracker
This is a manually grueling task, which by looking at these bugs, no one
else is doing. I'd like to turn that bit back on so we can actually get
attention focused on actionable bugs.
Any objections here?
No objection, just a remark:
One issue with auto-expiration is that it usually results in the
following story:
1. Someone reports bug
2. Triager notices NEW bug, asks reporter for details, sets INCOMPLETE
3. Reporter provides details
4. Triager does not notice reply on bug since they ignore INCOMPLETE
5. Bug expires after n months and disappears forever
6. Reporter is frustrated and won't ever submit issues again
The problem is of course at step 4, not at step 5. Auto-expiration is
very beneficial if your bug triaging routine includes checking Launchpad
for "INCOMPLETE bugs with an answer" regularly. If nobody does this very
boring task, then auto-expiration can be detrimental.
Erm, I was thinking it was set back to the former state. That sounds
something we can automate, nope ?
I can volunteer, my only concern is about the limited bandwidth I have.
Is anyone in Nova checking for "INCOMPLETE bugs with an answer" ? That's
task 4 in https://wiki.openstack.org/wiki/BugTriage ...
We already have trivial bug monkeys that are chasing up trivial
bugfixes. That sounds something we can discuss as an extent to the
trival bug chase until the point I mentioned above is provided IMHO.
-Sylvain
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
