On Tue, 2010-08-10 at 10:19 +0800, Adam Harvey wrote:
> I could not disagree more. I think one of the key lessons we should
> have learned out of the whole 6.0 saga was that "release early,
> release often" is a good thing
I will no support the release of trunk overly actively as long as the
"type hints" are as they are but on a general note:
Yes. Release early, release often is a good thing. What I'd also like is
to have a Ubuntu-like support model. Where we have one LTS (long term
supported) version (now for instance 5.3) which will get bug fixes for
quite some time and an "early access" version (5.4) which will receive
updates until the next "early access" (5.5) is there.
Reasons:
* Give people early access to features
* Motivate developers as their additions are in a reachable future
* Give users the chance to stay on the LTS version without having
to do the full update on every release
* Reduce the number of changes in "bugfix" releases
the whole idea in ASCII art:
Version Time ->
5.3 ****************+++++
5.4 |*****
5.5 || *****
5.6 || | *****
6.0 || | | ****************
6.1 || | | | *****
|| | | | |
|| | | | ^ Release date 6.1.0
|| | | ^ Release 6.0.0, 5.3 goes to extended support (security
only)
|| | ^ Release 5.6.0, 5.3 stays in support, 5.5 EOL
|| ^ Release 5.5.0, 5.3 stays in support, 5.4 EOL
|^ Release 5.4.0, 5.3 stays in support
^ now
So we'd always have three branches, while two only receive bug fixes,
plus one branch for the next milestone.
johannes
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
