Re: php 4.1
| From: | Hartmut Holzgraefe | Date: | Tue, 14 Nov 2000 07:31:32 +0000 |
| Subject: | Re: php 4.1 | ||
| References: | 1 2 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-38029@lists.php.net to get a copy of this message | ||
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