Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53415
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain schlueters.de from 217.114.211.66 cause and error)
To: dukeofgaming <dukeofgaming@gmail.com>
Cc: Derick Rethans <derick@php.net>, Pierre Joye <pierre.php@gmail.com>,
 PHP internals <internals@lists.php.net>
In-Reply-To: <BANLkTik9nF-eOMo8fxKoQuxGci88jeXqbw@mail.gmail.com>
References: <BANLkTi=5XWUh-tLbZ6MiJyMvrx4vype_mA@mail.gmail.com>
	 <alpine.DEB.2.02.1106201427110.3774@whisky>
	 <BANLkTik9nF-eOMo8fxKoQuxGci88jeXqbw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Mon, 20 Jun 2011 17:31:31 +0200
Message-ID: <1308583891.6296.4.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Can't vote yet, as RFC has "options" (Was: Re:
 [PHP-DEV] [VOTE] release process RFC)
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Mon, 2011-06-20 at 09:28 -0500, dukeofgaming wrote:
> On Mon, Jun 20, 2011 at 8:30 AM, Derick Rethans <derick@php.net> wrote:
> >
> > I am not generally against this RFC, but this point needs to be
> > discussed first IMO. As having 5 active branches at the same time for
> > the "multiple major releases" option is *not* workable.
> >
> 
> If its because of the constant merges, it would be workable if a DVCS was
> being used =)

Even then it is hard. The "pure" merging is one thing. But for merging
you first need to evaluate whether the patch is needed in the branch and
test the patch on every branch. Over time the branches will diverge.
Even if a patch applies it might be the wrong thing for a branch.
And then every of these branches should be released. For a release one
needs QA cycles etc.

johannes