Comment 5 for bug 668268

Perhaps we should take this to the list?

On Tue, Nov 2, 2010 at 7:38 AM, Curtis Hovey <email address hidden> wrote:
> Making it high does not commit anyone to fix it either :( This send the
> message that this will get done if the community ignores it.

I don't think it sends that message, because Launchpad bugs isn't
primarily a work queuing system. Importance is an amalgum of impact on
users and the relative priority the project community has given the
bug.

We can easily have bugs in high that noone touches for years, and low
ones that get done immediately. Our work queueing system is actually
Kanban, which further reinforces the disconnect. The impact on users
of being unable to remove data is significant. And the operational
impact is doing high risk operations.
...
> As a LOSA I would say "I will not run SQL to change comment, full stop".
> Then engineers have to stop work, re-prioritise, and make a solution
> that does not burden anyone else.

That would be a very hostile inter-team dynamic to observe, and I
would be very sad to see it happen. Our mutual jobs - LOSA + LP devs
requires meeting the needs of 4 groups: casual and power users,
operators and developers.

If we've been building poor implementations in silos, thats totally a
LP dev quirk and something we should just fix.

-Rob