Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:49306
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.161.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=gDXzcxhN+LUllTfoqmwhJPVZwtxKR4sjPQJGXC4ovyn+npyK8Ih3nJWQ+0msPasnPD
         p5AT9SELKC2agRR9KAJyhHREek+hu5awQGEi0GaBxFRAwGoMpsPD0uGenFd8z/ItgV7b
         lPaXyjLyDw8qATTK4rIymRUvYXUOXLlSQBJZc=
MIME-Version: 1.0
In-Reply-To: <4C616E48.9080309@php.net>
References: <AANLkTinAy_93RNH85zLpGo11_2eBYBewxg+=KaPicX4e@mail.gmail.com>
	<AANLkTi=Dv3AtH3BiTUgZwBuTLU30AF=3+5rr9aUUVzGG@mail.gmail.com>
	<AANLkTi=o-ssPwwhO3naDC6B55=bD5uRGvUm+L30z8qGr@mail.gmail.com>
	<1281429940.969.2093.camel@guybrush>
	<255073A3-5250-4962-875A-7B2E69E40A48@pooteeweet.org>
	<1281450642.969.2575.camel@guybrush>
	<alpine.DEB.2.00.1008101611200.29410@kossu.derickrethans.nl>
	<4C616E48.9080309@php.net>
Date: Wed, 11 Aug 2010 04:07:49 +0200
Message-ID: <AANLkTinStvdtsu-jRu=do+GmamduETygmzV48PmGjgMF@mail.gmail.com>
To: Sebastian Bergmann <sebastian@php.net>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Version management
From: pierre.php@gmail.com (Pierre Joye)

On Tue, Aug 10, 2010 at 5:20 PM, Sebastian Bergmann <sebastian@php.net> wro=
te:
> Am 10.08.2010 17:14, schrieb Derick Rethans:
>> I think our current way work pretty well. There is 5.2 which is
>> security-fix supported, 5.3 that is supported and trunk/5.4 that's on
>> the way to alpha.
>
> =A0This only works if manage to keep the time between "new code is
> =A0committed to trunk" and "new code is released" under a year. Otherwise
> =A0developers get frustrated.
>
> =A0If we manage to release a PHP 5.X.0 release every year, we are a lot
> =A0more predictable. Which is good for downstream as well.

That's exactly what I keep asking. It also requires some changes about
features addition in stable releases, bugs fixes and release life
cycles. All these words sounds like a nightmare to Derick&co, but
that's something we have to go through. It is the only way to have
controllable and plan-able releases (for us, our users and the
distros).

Cheers,
--=20
Pierre

@pierrejoye | http://blog.thepimp.net | http://www.libgd.org