On Wed, Jun 2, 2010 at 6:28 AM, James Westby <email address hidden> wrote:
> Well, that depends on how you are treating the bug.
>
> "packages aren't always up to date" - that's like filing a bug saying
> "this software has bugs", we can fix it, but it doesn't help in
> pointing to the things that need fixing.
I don't think that analogy is all that useful to thinking about the
problem. I'd rather think about it like uptime in a web service: we
can tell when its down, and we should react by bringing it up, and
resourcing the ops staff appropriately to be able to respond; and
resourcing the dev team appropriately to be able to fix
root-cause-is-a-bug issues.
On Wed, Jun 2, 2010 at 6:28 AM, James Westby <email address hidden> wrote:
> Well, that depends on how you are treating the bug.
>
> "packages aren't always up to date" - that's like filing a bug saying
> "this software has bugs", we can fix it, but it doesn't help in
> pointing to the things that need fixing.
I don't think that analogy is all that useful to thinking about the
problem. I'd rather think about it like uptime in a web service: we
can tell when its down, and we should react by bringing it up, and
resourcing the ops staff appropriately to be able to respond; and
resourcing the dev team appropriately to be able to fix
root-cause-is-a-bug issues.