Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76393 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 71093 invoked from network); 6 Aug 2014 13:25:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Aug 2014 13:25:43 -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:60077] helo=mail-qg0-f48.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A4/70-02707-5DC22E35 for ; Wed, 06 Aug 2014 09:25:42 -0400 Received: by mail-qg0-f48.google.com with SMTP id i50so2610711qgf.7 for ; Wed, 06 Aug 2014 06:26:08 -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; bh=b9lLDMVQ92qAUD7Fdr4SuWhGrl1nBX6qQ0ccsuaVOak=; b=LxQDKbBXGdglz+sfycD45zsFdzPsZkvkVfZSyRk5zqNVdyxgEsOjXe4McTQR9db2mi f5RwegyNeWYN2e2qZigtwI05KpS2oonXEfAyyosVlt3gq2Uni1z9005kB0UreX55PUaf 0BE8rav1UN7ZsXxCO33A/9D/XBT/etenOsxyiZ3KEerjUo1DNTZCJQNQVRJV6FPEsQDZ KP/7OuxHfZDKCYLG1lvZ8X73MOCgxEukunxnvlxT0AFDXwpvKffjAN6UNjYT3xmOz6YU ekaW/aWQ30Q5D4p2lgPMshIn3Mw8gIqB3UZNtvsMg6FXllkfxhGfIJwcTJCwdsXFHNdK /MXw== MIME-Version: 1.0 X-Received: by 10.224.127.131 with SMTP id g3mr17406640qas.0.1407331568700; Wed, 06 Aug 2014 06:26:08 -0700 (PDT) Received: by 10.140.24.54 with HTTP; Wed, 6 Aug 2014 06:26:08 -0700 (PDT) In-Reply-To: References: <5a5c7d37c2115f52a58d82d489540a6d@mail.gmail.com> <79d5d0a1410487d543d37ba573b392a9@mail.gmail.com> Date: Wed, 6 Aug 2014 15:26:08 +0200 Message-ID: To: Dmitry Stogov Cc: Zeev Suraski , Dan Ackroyd , PHP internals Content-Type: text/plain; charset=UTF-8 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:19 PM, Dmitry Stogov wrote: > On Wed, Aug 6, 2014 at 5:11 PM, Zeev Suraski wrote: > >> Dan, >> >> Votes area almost never pre-announced. I have no problem with changing >> this >> habit, but I do have an issue with changing it retroactively for a >> particular vote. >> >> Regarding your points, there's a mandatory discussion period during which >> you should have brought these comments, instead of now. As a matter of >> fact, discussion about PHPNG died out more than a week ago, to the level >> that Dmitry even suggested we avoid wasting time and vote sooner (but that >> goes against the rules so we didn't do that). >> >> If you think the RFC is incomplete in its details and that you can't vote >> over it then you can of course withhold your vote or vote no. >> >> To your specific feedback, there's a migration document to extensions >> linked >> from the RFC, and shared here on internals about 10 days ago: >> https://wiki.php.net/phpng-upgrading >> I added another link to it from the 'RFC impact' section, as perhaps that's >> what prevented you from seeing it. >> >> I believe it's impractical to keep shared codebases for extensions between >> PHP 5.x and PHPNG. Dmitry - please correct me if I'm wrong... >> > > Some extension might require just few changes and they may share codebase > for PHP and PHPNG, however it's going to be really difficult for very > engine depended extensions like xdebug. 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. -- Pierre @pierrejoye | http://www.libgd.org