Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:76398 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 86309 invoked from network); 6 Aug 2014 15:37:40 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Aug 2014 15:37:40 -0000 Authentication-Results: pb1.pair.com header.from=danack@basereality.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=danack@basereality.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain basereality.com from 74.125.82.174 cause and error) X-PHP-List-Original-Sender: danack@basereality.com X-Host-Fingerprint: 74.125.82.174 mail-we0-f174.google.com Received: from [74.125.82.174] ([74.125.82.174:45461] helo=mail-we0-f174.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B1/03-02707-2CB42E35 for ; Wed, 06 Aug 2014 11:37:39 -0400 Received: by mail-we0-f174.google.com with SMTP id x48so2811695wes.5 for ; Wed, 06 Aug 2014 08:38:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=nOuTDBGJ/mgOkTxzjl+u4PRMK9ETZqVjZGNPnGquFME=; b=T+dR26hFKGiHc+8i6DTCgk3Lwh6aTC1w+zgIEUor7B39r1EhKE7zgDxY1wCMB49JYb dVLwpkxAA06O4pSKWCVEsQym5CSVwQezlDiyVKfefPmOmkQldF9jUcppV3I5Y1Txgh15 aNZE3yC8/7SJ/PQkbyaBst4pVshb9JnuJoL+82cLybgTjA8Pjh9vD7ooPmAtFcrBhIQl QV5T/I1yA7LQqwnk+4saXPUQ3ZdJflvxfQ/ZHl93qi6BPzUCKMU5VZN4nI033yVGNUp4 JcsF5nFGA2VEymLmjfjYwQGZxp7LrnAQ2wmlTeQmob17kWgWiyCX5QPonQSX4csmCy2D Ux9A== X-Gm-Message-State: ALoCoQl5FDijNqPALYerSBuHD0eP+SNoJ5lFtJagnvy/iiKNdmLkY7a3QCSkSFzze2hwsF7MtJkL MIME-Version: 1.0 X-Received: by 10.194.60.35 with SMTP id e3mr17567277wjr.12.1407339485923; Wed, 06 Aug 2014 08:38:05 -0700 (PDT) Received: by 10.217.10.137 with HTTP; Wed, 6 Aug 2014 08:38:05 -0700 (PDT) X-Originating-IP: [212.159.149.212] In-Reply-To: <79d5d0a1410487d543d37ba573b392a9@mail.gmail.com> References: <5a5c7d37c2115f52a58d82d489540a6d@mail.gmail.com> <79d5d0a1410487d543d37ba573b392a9@mail.gmail.com> Date: Wed, 6 Aug 2014 16:38:05 +0100 Message-ID: To: Zeev Suraski Cc: PHP internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [VOTE] Move the phpng branch to master From: danack@basereality.com (Dan Ackroyd) Hi Zeev, >I have no problem with changing this >habit, but I do have an issue with changing it retroactively for a >particular vote. Agreed, changing rules retroactively is bad. Considering improving practices for the future is good. >To your specific feedback, there's a migration document to extensions linked >from the RFC, and shared here on internals about 10 days ago: Thanks for that document. It would also be really useful if you could add a link to two commits of a non-trivial extension that has been migrated, with one commit before, and one commit after the migration. That would allow people like myself who only rarely dip into PHP internals to see the differences actually applied to code. cheers Dan On 6 August 2014 14:11, 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... > > Zeev > >> -----Original Message----- >> From: Dan Ackroyd [mailto:danack@basereality.com] >> Sent: Wednesday, August 06, 2014 4:01 PM >> To: Zeev Suraski >> Cc: PHP internals >> Subject: Re: [PHP-DEV] [VOTE] Move the phpng branch to master >> >> Hi, >> >> It would be good if people announced that they were going to open things >> to >> vote with a warning, rather than just throwing the voting open. >> >> The RFC is nowhere complete in it's details for people to make rational >> decisions. e.g. the section on 'RFC impact' has this for the impact on >> extensions. >> >> "Existing extensions will have to be updated to reflect the new data >> structures >> and updated APIs. Much of this work is already done for most of the >> extensions bundled with PHP, but there are still extensions that need to >> be >> ported, and most of the extensions in PECL will have to be ported." >> >> That doesn't provide anything close to actual information about what needs >> to >> be done to port the extensions. There is no information about how >> extensions >> can support current PHP and PHPNG at the same time....which they will need >> to do for the next couple of years at least. >> >> >> cheers >> Dan >> >> >> On 6 August 2014 13:36, Zeev Suraski wrote: >> > I opened the voting on the phpng RFC: >> > >> > >> > >> > https://wiki.php.net/rfc/phpng#vote >> > >> > >> > >> > Voting ends on Thursday, August 14th. >> > >> > >> > >> > Please vote! >> > >> > >> > >> > Zeev