Sorry, the joke went right past me.
I was drawing the distinction between a crashing bug in something that
you build and give/sell to others, which is as bad as it gets, and a
crashing bug that causes the IDE to die while you're developing
software. That's bad too, but not nearly as bad.
On Apr 8, 2004, at 8:50 AM, Dar Scott wrote:
On Thursday, April 8, 2004, at 09:35 AM, Geoff Canyon wrote:
-- Is it crashing people in Revolution?
I have noticed that I have been crashing.
Dar
If the issue isn't in bugzilla, please enter it. If it is, great.
regards,
Geoff Canyon
[EMAIL
Hi guys,
After seeing some blocking bugs (that crash RR) that never got a reply,
it would be nice to know how to make issues that are important and cause
delays in software delivery be responded sooner.
Votes on a bug seem to be more important that bug criticallity it seems.
If I lay 90 of my
I'm in the process of going through all the bugs. When I'm done, all of
them will be assigned to a release of Revolution, which (for the
record) doesn't absolutely guarantee they will be fixed in that
release, but gives a good indication.
The criteria (roughly -- off the top of my head) are:
On Thursday, April 8, 2004, at 09:35 AM, Geoff Canyon wrote:
-- Is it crashing people in Revolution?
I have noticed that I have been crashing.
Dar
___
use-revolution mailing list
[EMAIL PROTECTED]
