Re: CVS Account Request

In general, I'm not particularly fond of the PHP 4.1 idea. I remember how things were when PHP 3.0 and 4.0 were both in development, and it wasn't that pretty. It's a very similar situation - PHP 3.0 was the stable version, 4.0 was the unstable version gradually becoming more and more stable, and the headache of synchronizing the two trees was pretty horrible. We only got away with it because so many parts of PHP were written from scratch, making the relevant PHP 3.0 code obsolete. I don't think (and I certainly hope) it won't happen again :) I would keep this kind of separation for truly major upgrades of the language, and adding a feature here or an extension or function there, despite the fact it may be a huge benefit to end users, is not a major upgrade from a technical point of view. I do like the idea of creating a branch for each release, and moving all development to the main branch a week or two before releasing, allowing only verified bug fixes in. Zeev At 01:38 16/11/2000, André Langhorst wrote:

I think that the kind of QA we're trying to develop for PHP is functional-level, and not source level. It's not going to address the security concerns involved in giving people CVS write access very quickly.

both, combine what harmut and I had to say (thread php 4.1, last mail from harmut will be sufficient) with results of a thread months ago regarding "no-code-freeze-in-PHP-for-more-than-few-days-before-release" with results of *this* thread and results of the thread (a few days ago) regarding "branches" and there we are... andré

-- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/