Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76406
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4ED7146272E04A47B986ED49E771E347BBE9680FEF@Ikarus.ameusgmbh.intern>
References: <5a5c7d37c2115f52a58d82d489540a6d@mail.gmail.com>
	<CAEZPtU5-FcWCDasb8NoqPANsriZ+A451M95hE=-w9LWwJbSefg@mail.gmail.com>
	<4ED7146272E04A47B986ED49E771E347BBE9680FEF@Ikarus.ameusgmbh.intern>
Date: Thu, 7 Aug 2014 12:57:00 +0200
Message-ID: <CAEZPtU4Wdkx-AoN9795c5cdLQEVdvHopb+e0vtUR5cE6B-NOsA@mail.gmail.com>
To: Christian Stoller <stoller@leonex.de>
Cc: Dmitry Stogov <dmitry@zend.com>, PHP internals <internals@lists.php.net>, 
	Dan Ackroyd <danack@basereality.com>, Andrea Faulds <ajf@ajf.me>, Zeev Suraski <zeev@zend.com>
Content-Type: multipart/alternative; boundary=047d7bdc875ebb1b78050007f2cb
Subject: RE: [PHP-DEV] [VOTE] Move the phpng branch to master
From: pierre.php@gmail.com (Pierre Joye)

--047d7bdc875ebb1b78050007f2cb
Content-Type: text/plain; charset=UTF-8

On Aug 7, 2014 8:13 AM, "Christian Stoller" <stoller@leonex.de> wrote:
>
> From: Pierre Joye [mailto:pierre.php@gmail.com]
> > On Wed, Aug 6, 2014 at 3:45 PM, Andrea Faulds <ajf@ajf.me> wrote:
> >>
> >> On 6 Aug 2014, at 14:26, Pierre Joye <pierre.php@gmail.com> wrote:
> >>
> >>> For the exts I tried while I was testing/fixing phpng a couple of
> >>> weeks ago, I'd to say that maintaining the same code base for phpng
> >>> and 5.x is simply too hard, way too many APIs changes, many of them
> >>> cannot be detected at compile time, introducing many many new #ifdefs
> >>> along other things. I will maintain a separate branch. The only thing
> >>> I worry about is how I will manage releases in pecl. I have no clean
> >>> solution now, or maybe one release with two branches bundled. Separate
> >>> releases could work too but I will try everything possible to do not
> >>> have to do that, or to have to do that as it is really painful to do.
> >>> Maybe I can manage to implement something in pickle to ease this work.
> >>> Ideas welcome.
> >>
> >> Perhaps for these extensions, it is best to not make it work with
> >> both versions, but instead have a 5.x version and a phpng version,
> >> and continue to maintain both separately? I wonder if that might
actually
> >> be less work than trying to keep a single version working on both.
> >
> > This is what I just said. But the problem is then how to release them.
> > An extension will release 2.0.0, how do you release it? 2.0.0-7 and
> > 2.0.0 for 5.x? Packaging, branching, etc. will be painful too. The
> > whole flow many projects uses now will have to change. This is
> > something I have to think about, not sure what is the best solution
> > yet.
> >
> > --
> > Pierre
>
> I'd say the best way is to create a new major version for the extension
> branch which works with phpng.
> So 2.0.0 for normal and 3.0.0 for phpng. This would make it possible
> to maintain two branches for both versions. But I don't know if this is
possible
> with pecl.

Not sure. It means 5.x versions won't get any major version then, which is
very unlikely for many exts.

Cheers,
Pierre

--047d7bdc875ebb1b78050007f2cb--