There are some ambiguities I need resolved to get the rules right for expiration.
I think we need to make a distinction between the bug (the reported problem) and a bug task (what the bug affects and where it will be fixed).
A bug may have many tasks, each affecting a different thing, a product, product series, a distro, a distro series, a distro source package, a distro binary package. Each task for a hypothetical bug may have a different status. For example in bug <https://bugs.launchpad.net/ubuntu/+source/celestia/+bug/30970>
Baltix is Confirmed, Celestia is Incomplete. Do we Expire Celestia?
A bug task may be fixed in multiple places like in Ubuntu, debian, gnome. For eample in bug
<https://bugs.launchpad.net/ubuntu/+source/gnomescan/+bug/64976>, an upstream task is New, and the Ubuntu task is Incomplete. Do we set the Ubuntu task to Expire?
There are some ambiguities I need resolved to get the rules right for expiration.
I think we need to make a distinction between the bug (the reported problem) and a bug task (what the bug affects and where it will be fixed).
A bug may have many tasks, each affecting a different thing, a product, product series, a distro, a distro series, a distro source package, a distro binary package. Each task for a hypothetical bug may have a different status. For example in bug <https:/ /bugs.launchpad .net/ubuntu/ +source/ celestia/ +bug/30970>
Baltix is Confirmed, Celestia is Incomplete. Do we Expire Celestia?
A bug task may be fixed in multiple places like in Ubuntu, debian, gnome. For eample in bug /bugs.launchpad .net/ubuntu/ +source/ gnomescan/ +bug/64976>, an upstream task is New, and the Ubuntu task is Incomplete. Do we set the Ubuntu task to Expire?
<https:/