Development Discussion Board

It's actually quite trivial. There's a mod for this for 2.0.x, and I think it was all of about six lines of code, if that.

We wait for you to start your browser, then rush to post new bugs so that when you do go to the bug listing, it's longer than before.

jojobarjo32 wrote: (hey guys, don't torture french please )

If we can tolerate the (sometimes painfully) broken English sometimes spoken here, you can handle a little fudged French.

But there are too many bugs now. Developers fix 8 bugs per day and users add new 8 bugs per day, and the like it'll be in next days (weeks).

That's pretty much the reason. Of the 77 bugs currently open, 53 (69%) of them have been reported on or since 01 April (about five per day), 16 (21%) in ...

Those that know what they're doing will perform the testing on live or semi-live data, confident that they can keep up with changes. Those that don't know what they're doing will either not do it, or be told why they're not getting the support they want when something breaks. The devs rely on the ...

Maybe you knew that nixx would get yours, so you went back in time to ensure that you would get onto the team to guarantee yours and deny his!

Build a time machine (or purchase one for a few billion dollars) and go back 11 months to when the Conquering Olympus Berties were sold and you can then usurp the one that I got instead.

How do we know that's not what you did? You could have been the one to build a time machine and took nixx's ...

With a hammer.

It's just an error message that gets displayed when something isn't right.

Companies have budgets and deadlines to stick to. In the case here there is no profit nor a deadline. It will be ready when it's ready. Therefore they can take as long as they want.

The key here is "when it's ready," which you know as well as I does not have to mean "when the bug count is down ...