Re: Suggested direction for the PHP QA Group

> On Fri, 30 Jun 2000, Zak Greant wrote: > > Secondary Goal: > > Help streamline the bug reporting process. > > This can be done by: > > - Closing spurious bug reports > > Good. > > > - Confirming existing bug reports > > Yes! Even better. If we have a QA person's confirmation on the bug with > a possible list of steps to reproduce it, it would make it that much > easier to find and fix the bug. I think some of those steps should be made clear... 1. Identify exactly what the bug is, if the user hasn't done so: The opendir function will not work when it is called more than once in a PHP script. On the second successive call to opendir, PHP complains saying "...". 2. Identify all related bugs that you can find (duplicates, etc). 3. Give the specifics, OS, script, configuration, other special considerations... 4. If you can, it helps if you go through the source and say: The problem comes in line ..., where "..." 5. If you can, offer a fix. Sterling