PureBasic Forums - English

Bugs usually can have different priorities, and the highest priority
is a showstopper.
A showstopper is a bug that makes the product unusable.
Compiler crashes are showstoppers. The compiler generating wrong
code is a showstopper. The product/IDE does not start is a showstopper.

Such *highest priority bugs* get usually fixed as soon as possible by most companies.
They release a fix asap and call it quickfix, hotfix or version "major.minor.BUILD5380".

Showstoppers don't happen every day, but if they happen, they should get fixed immediately.

A spelling mistake in the documentation is no showstopper, so it does not have
the same priority.

So my suggestion, request and wish is: assign different priorities to bug reports,
internal if you don't want a public bug tracker.
And most important: fix showstoppers as soon as possible and provide the
customers a fixed version.

Waiting for the next version is a very long time with a showstopper that makes the
product unusable. It's bad for the reputation of PureBasic, the company and the developers
behind PB.

Not to disagree with bugfix and/or feature priorities, but in my 6 years experience with PureBasic, the cure for a "showstopper" is to return to the previous version until it's fixed. If it's really a showstopper across multiple versions, it must be pretty obsure and fairly easy to work around.

cheers

Hi danilo

Just FYI in case you missed this...

I asked a question about that in the past, fred stated they already prioritize bug fixing and talked about showstoppers here:

http://www.purebasic.fr/english/viewtop ... 05#p302605

I understand that your request is something a little different (fred was talking about bugs in the beta cycle).

Thank you luis!

I had a showstopper with 4.51 (x64 generating wrong code, found while writing gDrawing),
reported on 8th of July 2011 by ts-soft (moved to a secret forum now), fixed with PB 4.60.

I had the feeling that it took too long to fix the showstopper, but maybe i am just too impatient and demanding again.

I apologize!