Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:58920
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <e9b5653ac45993b9fdec413f0df7bc82.squirrel@www.l-i-e.com>
References: <slrnjl05bd.mfm.dsp@experimentalworks.net>
	<CAH-PCH72jbCycqnBbkg2-H2uej_0LSyc8DNvjvys9SwkDQS8Ug@mail.gmail.com>
	<e9b5653ac45993b9fdec413f0df7bc82.squirrel@www.l-i-e.com>
Date: Tue, 13 Mar 2012 12:12:05 -0700
Message-ID: <CAKOpQSxm7mtQxTOLH+yHV7PfjN+fRBP33+5dVvYUayOA+GLz6A@mail.gmail.com>
To: Richard Lynch <ceo@l-i-e.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary=f46d043892b57976a104bb24a20a
Subject: Re: [PHP-DEV] HEADS UP: 5.4 branch is open again
From: kris.craig@gmail.com (Kris Craig)

--f46d043892b57976a104bb24a20a
Content-Type: text/plain; charset=ISO-8859-1

Yes, IF you're using a proper branching model.  If you're just using it the
same way you'd use Subversion, which currently is the direction we seem to
be moving in, those advantages are mostly negated.

I agree that PHP 5.5 (and maybe even 5.6, etc) should come before PHP 6.
That being said, at some point a parallel development workflow might be
prudent IMHO, but even that would be a ways off I think.

--Kris


On Tue, Mar 13, 2012 at 11:55 AM, Richard Lynch <ceo@l-i-e.com> wrote:

> On Fri, March 2, 2012 4:26 am, Ferenc Kovacs wrote:
> > If we can agree upon the next version number beforehand, and we decide
> > that
> > we will go with the major release (be that php 6 or 7, whatever), we
> > don't
> > to do anything right now, we can branch the version from trunk/master,
> > when
> > the time comes.
> > If we can't agree upon the next version number, or we agree upon that
> > there
> > will be an 5.5 version, I think it would make sense to create a branch
> > for
> > it ASAP, so there is place (trunk/master) for the approved but
> > backward
> > incompatible changes, and people don't have to hold patches.
> > What do you think?
>
> If I was in charge, and thankfully I'm not, I'd just create 5.5 and 6.0
>
> If you have patches that don't break BC, put them in both. If you're
> too busy to do both, put it in 6.0  Somebody will back-port or not,
> based on their relative need/availability or not.
>
> If it breaks BC, put it in 6.0
>
> Or perhaps I misunderstand the tiny bit I thought I "got it" of the
> point of using Git in the first place...
>
> Branches and merges are supposed to be seamless, right???
>
> --
> brain cancer update:
> http://richardlynch.blogspot.com/search/label/brain%20tumor
> Donate:
>
> https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FS9NLTNEEKWBE
>
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d043892b57976a104bb24a20a--