@Scott, we don't use Medium for scheduling anymore: it is effectively
meaningless. You can see our policy at https://dev.launchpad.net/BugTriage (and links from there to the
reasoning behind it)
So this change is merely reflecting the *existing* reality that it
wasn't scheduled, and as we have more bugs coming in than going out,
it never would be reached by simply working-the-queue.
To get it fixed it needs one of:
- being part of a feature we work on - we scan for related bugs,
group and work on them together. We've just done an email feature, and
I'm not aware of another in the current plans we have (e.g. next 6-12
months)
- a patch from someone personally interested in fixing it
- to be escalated via the stakeholder process (there is an Ubuntu rep
for this, uhm, the name currently escapes me. It might be bryce).
@Scott, we don't use Medium for scheduling anymore: it is effectively /dev.launchpad. net/BugTriage (and links from there to the
meaningless. You can see our policy at
https:/
reasoning behind it)
So this change is merely reflecting the *existing* reality that it
wasn't scheduled, and as we have more bugs coming in than going out,
it never would be reached by simply working-the-queue.
To get it fixed it needs one of:
- being part of a feature we work on - we scan for related bugs,
group and work on them together. We've just done an email feature, and
I'm not aware of another in the current plans we have (e.g. next 6-12
months)
- a patch from someone personally interested in fixing it
- to be escalated via the stakeholder process (there is an Ubuntu rep
for this, uhm, the name currently escapes me. It might be bryce).
HTH,
Rob