I understand what you're saying, but my statement was concerned with
the fact that it was your demo: Not knowing what the demo was I opted
for the general view that this was reported by a standard user, who
is often naive, which I judged from the 'bug report'.
Most naive users do not understand the 'bug reporting process' and
many do not want to be educated because they see no benefit to it:
They just want to play the game (or whatever the app is).
Cheers,
Luis.
On 18 May 2007, at 16:45, Chipp Walters wrote:
On 5/18/07, Luis <[EMAIL PROTECTED]> wrote:
On 18 May 2007, at 05:30, Chipp Walters wrote:
>
> Heck, I wrote that demo and even I can't figure out what this guy
> is saying!
>
Surely that's where two way communication comes in handy?
With Rev having hundreds of bugs to go through, anyone serious about
getting their bug fixed would be wise to create:
1) a clear explanation of the bug
2) a recipe for replcating it
3) if possible, a demo stack showing it
Furthermore, those who wish their bugs fixed can also do a bit of
research by contacting other developers here to confirm the bug before
posting it.
Typically, when I discover a bug in Rev, I try first to break it down
into it's simplest components and try and create the most
straightforward and basic recipe for repeating it. Then I create a
simple bug demo stack, post it online and ask others to verify it.
Once verified, I then post the bug, with the stack, to bugzilla. I
have found this methodology has enabled most all of my reported bugs
to be fixed in a very timely matter.
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
