RE: [PHP-QA] Is a new bug reporting system needed?

j>> Over 50% of the bugs require some kind of testing specialization, i.e. j>> Adabas, Oracle, Compiling under Debian etc installation problems. I That's netural, because general-purpose bugs get fixed pretty fast as soon as anybody turned attaention to it (that is not necessary happens soon, some bad-worded report can lie there for month until someone has a couple of hours to understand what's the real problem). Only "my fooBase doesn't work on barOS" stick for a long time - you need fooBase and barOS to see what's up. j>> Of the rest, I tried about a dozen at random and couldn't reproduce any j>> of them, let alone find anything to fix. Then if they aren't clear or old and not reporoduceable, IMHO you should require feedback from the user. If they are too old (like, reported for Beta1) just close them and let user reopen if it's still there. Also, I think we need one bug reporting category for every module, except maybe only basic ones. Stuff like GD or PDF obviously need to be separated from other general stuff. -- Stanislav Malyshev stas@zend.com +972-3-6139665