Re: PHP/QA Update
| From: | Sterling Hughes | Date: | Wed, 26 Jul 2000 23:26:17 +0000 |
| Subject: | Re: PHP/QA Update | ||
| References: | 1 | Groups: | php.dev php.qa |
| Request: | Send a blank email to php-dev+get-26414@lists.php.net to get a copy of this message | ||
> Hello All,
>
> I thought that I should update everyone on what has been happening
recently
> with the QA effort.
>
> So far the bug cleaning work seems to be going well. The bug packs are
> getting finished quickly. The developers also seem to be actively working
> on closing many bug reports.
>
> We started with about 670 open bugs and have cut that number down by about
> one-third. Not bad for only having started 4 days ago!
>
> Here are the actual numbers.
>
> PHP 4 Bugs *
> ----------------
> Closed 1994
> Open 466 **
> Analyzed 30
> Suspended 6
> Duplicated 29
> Assigned 23
> Feedback 180
> ----
> Total 2728
>
> * All of the bugs - except for submissions received after the July 22 and
> bug packages 6, 13, 14, 16, 17, 18 & 19 - have been summarily reviewed.
We
> should be able to close another 30 or 40 bug reports after these packs
have
> been reviewed.
>
> ** 25 new open bug reports accumulated between the 22nd and today
>
>
> waldschrott has been churning through the bug reports at quite a steady
pace.
>
> Joey has been working hard on a series of persistant problems (like
> browser-caps - blech!)
>
> I have been trying to clear out as many simple or spurious bug reports as
> possible - I have mostly stayed away from any compilation, installation
and
> ISAPI problems.
>
>
> Regarding the status of the bug packs: I am sure that waldschrott will
have
> his remaining bug packs (16-19) finished in short order.
>
> jalal and Derick - do you have enough time to work on this right now - if
> not, then would you like someone to take them off of your hands?
>
>
> Once we have all of the bug packs reviewed, I propose that we go through
> the remaining bugs and do the following things:
>
> Remove or update old feedback status bugs
> Find all duplicate bugs
> Group remaining bugs into packages based on the type of bug.
> Try to validate the bug.
> Try to find core developers who can work on the fixes.
>
s/core/competent/; # W/ Regards to PHP's internals
I'm not a core developer, however I've got enough knowledge of PHP/Zend's
internals to fix a good deal of bugs, and I'd be willing to work on the
fixes.
-Sterling