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

> > The biggest problem seems to be too many open bugs - as many people have > > suggested, perhaps we should just focus on getting those cleared up. > > Definitely. I think one very simple but effective measure would > be allowing > the QA team to confirm bugs (perhaps with commentary). That'd allow the > developers to fix confirmed problems before looking at what's left. > > One other thing that would seem to be useful would be an [internal?] area > where we could flag certain features as needing examination. For example, > this afternoon I've been running in to a problem with heredoc output. It > seems to be related to the line termination used (Unix line termination > seems to be immune) but it's not quite that simple and I haven't > had time to > track it down exactly. It'd be handy if there was a place where QA people > with spare time could see items which have been flagged as behaving > suspiciously, see if they can make it break and then submit a > well prepared > bug report instead of the "$FEATURE fails weirdly" bug report that'd > probably be filed otherwise. I think these are all good ideas but I think for the moment, our time would be better spent trying to accomplish our main goal. Organizing a structure for the QA team and establishing procedure for testing the RCs is the primary reason this team was established. While I think all these issues need to be addressed, I think we should wait a bit before acting on them. If we can accomplish our primary goal, we will have made a huge stride in aiding the developers. Jason _______________________________________________________ Site Design, Hosting, and E-Commerce at www.webpipe.net