Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:107053
MIME-Version: 1.0
References: <076701d56978$86020910$92061b30$@php.net> <CADyq6sK4HektgfDpCCFR3=bumyPaf9vn=-WdvaboHybBQKd53g@mail.gmail.com>
 <078e01d5697c$5512bc10$ff383430$@php.net> <CAKws9z1EBSqCFy2wD3cEV49KDSJOd6tT04PrCkxG8+3Hb6WpTA@mail.gmail.com>
 <CAPKYkKw1EU3Qp6W7b19r4kMKPD1HntH+7NQSxSiDNcLXqPERMA@mail.gmail.com>
 <CAKuGYLRWF9jnS-Zs+uRFNN1pgRSvHFpW-FChgNq9Rk282AFFGA@mail.gmail.com>
 <CAPKYkKxUyeWWZY5OyDLtAYiDUYLkwyMjuc_Wq2Y++3C9CP6G1w@mail.gmail.com>
 <CANS-=pc7Av0+jSKNebb-iae+BpTt6_72kRSHSowb-hon4rxUgQ@mail.gmail.com>
 <31BD63BC-ACE0-4478-B241-E698D2D6F59C@newclarity.net> <CANS-=pexJhtBS=me8RDvg0+BjXWVqmONU4CDVyrGgcsia40YGA@mail.gmail.com>
 <CAJvSBVOm4FHAdr24vra5DrFJqqXXqh1g=c02RdgodWYPZDqd5Q@mail.gmail.com>
 <CANS-=pd9nMcTpNrcJMHKLv-W74KJqWQRmh55iZ-nKoS59iQSUw@mail.gmail.com>
 <77CA024D-3141-4707-8280-81CA78282AFA@newclarity.net> <a2b7c9e4-ee6d-2f71-808b-938272755e00@lsces.uk>
 <DAD96213-CDA9-4AB7-9F7C-3E73F6A00E3B@cschneid.com>
In-Reply-To: <DAD96213-CDA9-4AB7-9F7C-3E73F6A00E3B@cschneid.com>
Date: Fri, 13 Sep 2019 10:18:32 +0200
Message-ID: <CAEPJdumHtxBvUybiNASwWZzfYqAEAhxHfUtBa7Jyyb71EAuJ5g@mail.gmail.com>
To: Christian Schneider <cschneid@cschneid.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000000c529805926ae7d2"
Subject: Re: [PHP-DEV] Changing fundamental language behaviors
From: kontakt@beberlei.de (Benjamin Eberlei)

--0000000000000c529805926ae7d2
Content-Type: text/plain; charset="UTF-8"

On Fri, Sep 13, 2019 at 10:10 AM Christian Schneider <cschneid@cschneid.com>
wrote:

> Am 13.09.2019 um 09:41 schrieb Lester Caine <lester@lsces.uk>:
> > On 12/09/2019 23:16, Mike Schinkel wrote:
> >> Those who vote on this list will decide if breaking WordPress
> end-user's site bothers them or not.
>
> That's something too few people on this list seem to be aware of:
> Breaking other people's perfectly functional code because you believe in a
> different coding style is not something which should be done easily.
>
> > So we *DO* need an LTS version of PHP that will run perfectly functional
> websites for the next ten years while others create the next replacement
> for the likes of WordPress by moving framework functionality inside PHP ...
>
> I agree!
> Which means there will be additional burden on the PHP core developers as
> there will be another version to back port security fixes to for a long
> time. Also not a decision to be made lightly.
>

I would think that this is exactly what a company like Zend would charge
their customers for. Microsoft is doing it for free for 5.6, I imagine for
their bigger Azure customres here: https://github.com/microsoft/php-src

LTS versions should not be the responsibility of the core developers, they
are the responsibile of a legal entity with financial means that either
directly sponsors the OSS project (Ubuntu) or is downstream of the project
(RedHat).

PHP is entirely a community project of volunteers that is already hanging
by a thread given the workload.


> While I do like democracy I also agree with Zeev that it is too easy for
> people to vote yes on a breaking change even if they didn't think it
> through.
>
> So if you voted yes for any change of a notice/warning to an exception
> (which will break things) please reconsider!
> Is it really worth it? And if you really think so, could we make it
> opt-in? Or at least globally opt-out-able?
>
> - Chris
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--0000000000000c529805926ae7d2--