Comment 8 for bug 91925

I think some confusion as to how this will be implemented has arisen. I'd like to point out that:

  - We would only expire bugs in the Incomplete status
  - We would only expire bugs which were unassigned

I think it's really important that we do have an auto-expiration feature. The usefulness of a bug goes down dramatically once it has been open for more than a few months, and in my 10 years of experience working with bug trackers I am sure it's better that old bug reports be closed than stay around. Our objective is not to fix all bugs that exist in software (and Dijkstra would smile here): it's to fix the bugs which are most frequent and most relevant.

Note also that expiring a bug is a good way of telling people that if they want their bug fixed, they need to speak up and provide us with concrete information.

The bugs we'd consider for expiration in the Ubuntu context are the ones listed here:

https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=Incomplete&assignee_option=none&field.assignee=&field.bug_reporter=&field.bug_contact=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_cve.used=&field.has_no_package.used=

I am only curious right now as to what status the bugtasks should be moved to. A special status Expired? That would at least easily allow us to find and communicate what happened to them.