Re: We Want Quality
| From: | Zeev Suraski | Date: | Thu, 29 Jun 2000 20:53:03 +0000 |
| Subject: | Re: We Want Quality | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-22960@lists.php.net to get a copy of this message | ||
On Thu, 29 Jun 2000, Andrei Zmievski wrote:
> On Thu, 29 Jun 2000, rasmus@lerdorf.on.ca wrote:
> > I don't think shutting down CVS for 5 days is an option. There are too
> > many components at too many different stages of development to make this
> > work without annoying the hell out of the developers.
>
> Perhaps, "shutting down CVS" was a bit strongly worded. I think it would
> also be fine if the maintainers of non-essential extensions kept working
> on them (whlie it still would not reflect well on PHP if it was released
> with broken domxml or other extension). But, during RC cycle we should
> limit commits only to serious bug fixes and then start another RC after
> a few of them.
That's the way we do things anyway, because it's the right thing to do.
It's nowhere near what Sascha initially suggested and you followed up,
though.
Guys, I don't enjoy saying it too much, but we pretty much excel at
talking, and we're not nearly as good at implementing, when it comes to
the non-glorious issues, such as QA. We decided over 5 months ago that
we'd have a new regression suite, and so far, not a single byte of code
has been written for it. I'm in favour of one thing only - if someone
feels he can organize it, start doing it. Laying out a complex ruleset
with all of our requirements and wishlists is great, but it'll be
forgotten within a couple of weeks at most. If someone begins to do
something, there may be a chance.
The main issue here is that this job is boring and non glorious, which is
why I'm not too optimistic we'd find too many candidates, at least not
ones that would care to stay for a long time.
Zeev
--
Zeev Suraski <zeev@zend.com>
http://www.zend.com/