Re: php 4.1

Good proposal! Thanks for that good input! Because after reading Andre's postings I've got really angry... The reason is, that I have introduced PHP in the 2nd country (?? have read about the first only in the php-ref.-list) of my company (out of 140 countries), where MS is "burned in" in the minds. And now, a view months later, I have to consider to drop php again, even I use only the GD- and the MS-SQL extensions (which should be introduced long enough to be able to get used). But I can't defend all the calls from the users, and have only the choice about warnings and "cutted" texts, or an compete cgi-errors. But besides my personal situation: as long as there isn't also at least a little focus on quality (meaning working also on old bugs, and not only on new functions which cause often new bugs), you will strengthen the image the Open Source community has - and e.g. Linux still fights with - : "A hobbyist-system, not for prof. use". And such a reputation can't be the right one for the great work you do! Therefore I appeal to you: Please consider also the existing versions (bugs), and the documentation, even they are not that interesting! So far to my organisational opinion.... Best regards, Thomas Hartmut Holzgraefe wrote: > André Langhorst wrote: > > > > > We prefer saving 2nd digit version number changes to more > > > 'revolutionary' releases of the language. > > > > Ok. then do not rename it from 4.0.x to 5.x when engine 1.1 is released. > > I just tried to avoid that there are 17 versions of a 4.0 version as it > > happened to 3, there are so many nice numbers (1-9) besides "0" and I > > don´t think there will be 9 major+revolutionary releases before php 5 > > > > as PHP is diveded up into language and functions and consists of both, > > major changes in them should (could) also trigger a 2nd digit change > > (eg. apache 2 API is supported too now) > > what about a Linux-Kernel like numbering scheme? > > - declare 4.0 as stable, only bug and security fixing allowed > - start 4.1 as developement, this is where experiments take place and > new extensions are added > - 'grown up' extensions may be copied to the stable 4.0 version as > soon as they have become stable themselves > - new core features _may_ be ported back if and only if they can be > integrated into the stable version without module api changes > - every once in a while we take what has piled up in the developement > branch and decide what is going into a new stable version and what > is not yet ready for prime time but has to stay in a new developement > - whenever a new stable branch is going to come there will be a feature > and a code freeze phase for the developement branch until it is ready > for > release and a short phase after release before the new developement > branch is opened to get developers concentrated on stability instead > of new features ... > > -- > Harmut Holzgraefe hartmut@six.de > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net