Re: Making a release
| From: | Stefan Neufeind | Date: | Fri, 05 Mar 2004 13:22:10 +0000 |
| Subject: | Re: Making a release | ||
| References: | 1 | Groups: | php.pear.qa |
| Request: | Send a blank email to pear-qa+get-833@lists.php.net to get a copy of this message | ||
On 5 Mar 2004 at 13:33, Stephan Schmidt wrote:
[...]
> > So from my side I didn't find any grave bugs ... just wrote down
> > some suggestions I head. All in all: Well done!
> I think most of this stuff could have been (and some already has been)
> discussed during the proposal phase. I'm not quite sure what the tasks
> of the QA team is in detail... But thanks nevertheless for checking
> the code.
The main topic for PEAR QA are reacting to problems related to
quality. E.g. if a bug is very important or has been long standing
but the maintainer can't be reached, then PEAR QA should handle this.
Or if there are versioning-issues (like the 0.7-stable-release of a
package lately - which should have been 1.0 according to the rules)
we'll step in. However, since there has been recent discussion about
"maybe letting somebody look over the code before a release" this was
just a suggestion to clear those quite obvious errors before a
release. However, you haven't made any :-)) Well done!
So thank you for asking QA to have a look at the package. And don't
consider the points I mentioned really QA-related. It were just a few
minor points I came across during code-reading and that I wanted to
give you to maybe think over some points again. If you did everything
I mentioned intentional ("already discussed with Alan" etc.) that's
fine!
From my side I'd consider your package as very well done from the
quality-side. Don't get me wrong!
Thank you for your contributions. Keep up the good work
Stefan