Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76395 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 75882 invoked from network); 6 Aug 2014 13:53:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Aug 2014 13:53:59 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.48 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.192.48 mail-qg0-f48.google.com Received: from [209.85.192.48] ([209.85.192.48:40137] helo=mail-qg0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8A/51-02707-57332E35 for ; Wed, 06 Aug 2014 09:53:58 -0400 Received: by mail-qg0-f48.google.com with SMTP id i50so2678845qgf.35 for ; Wed, 06 Aug 2014 06:54:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=i2AaeeMYxOZUvoUbO+aO2JSqbjtwhzlvg07zN1g1z6g=; b=UyHCs2/hM8O8hpCzi7BQ6mgi5XpndMyx2jie20t1886gOx5QOJOGDT2t0mSwwHCAiy dS2rzpj7ASclyHtK07ylkzrlyL153IP1Taz7rRE3JMvgsbFSO1UnVmMyE49EQavTy2vJ nrryo9HYmyhU7AsEuhsFwjV74a7DeKZJuNEeXFdmE15KU4cxmp5MxSQOboh1rgVQpf/G QGyH71JzWgTLf57Bj5dt2cZRRPWeY/AodI2pyGct8wOf1IlnPlQ78rYANxbnpJOvodre SN+dzqaGOfOHmwKUxBLAHiVY8Em8DB3eA8esXLKFhCFNQmOyq8cWN4WaBXAZ6eDpJNdE 3Zrg== MIME-Version: 1.0 X-Received: by 10.224.119.193 with SMTP id a1mr17470634qar.18.1407333265272; Wed, 06 Aug 2014 06:54:25 -0700 (PDT) Received: by 10.140.24.54 with HTTP; Wed, 6 Aug 2014 06:54:25 -0700 (PDT) In-Reply-To: <3D4C74A8-0BFF-4B30-BBBB-D0005DD9C5F2@ajf.me> References: <5a5c7d37c2115f52a58d82d489540a6d@mail.gmail.com> <79d5d0a1410487d543d37ba573b392a9@mail.gmail.com> <3D4C74A8-0BFF-4B30-BBBB-D0005DD9C5F2@ajf.me> Date: Wed, 6 Aug 2014 15:54:25 +0200 Message-ID: To: Andrea Faulds Cc: Dmitry Stogov , Zeev Suraski , Dan Ackroyd , PHP internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] [VOTE] Move the phpng branch to master From: pierre.php@gmail.com (Pierre Joye) On Wed, Aug 6, 2014 at 3:45 PM, Andrea Faulds wrote: > > On 6 Aug 2014, at 14:26, Pierre Joye 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 ve= rsions, 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 tha= n 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. --=20 Pierre @pierrejoye | http://www.libgd.org