Revolution 2.8.1: a 240+ bug fixes/improvements! What about the remaining 1879?
Peter Alcibiades
palcibiades-first at yahoo.co.uk
Fri May 18 14:13:16 EDT 2007
Chipp, I think you may be drawing the wrong lesson. Of course the bug you
mention is not useful. The problem is that the database contains it. That
tells you something. Bill's remark, that the database contains lots of stuff
that is already fixed also tells you something. Its good news and bad news,
its good about the bugs. Its less good about the database.
People have enormous goodwill towards Rev. They will accept realistic targets
that are met, even if those targets are less than what they want, and less
than what the Rev team wants to deliver. I think part of what Joel is saying
may be: pick a quantified realistic goal, communicate it, and stick to it
and deliver it. Even if it not what people would have liked, they will like
this approach to delivering a given quantity of work much better than any
possible alternative.
Peter
> My point was to show all bugs are not created equal. How do you resolve a
> bug which starts:
>
> "RunRev doesn't work." --user
> "What's the problem." --RR
> "It's broken" -user
> "How can I help?" --RR
> "When I step on the pedal, it doesn't go forward!" -user
> "That's the mouse, and you're not supposed to step on it" -RR
>
> My only thought is I'd rather RR spend their valuable and precious
> bug-resolving resources on bugs which are clearly delineated.
More information about the use-livecode
mailing list