Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:90591
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain pascal-martin.fr designates 91.121.85.26 as permitted sender)
To: internals@lists.php.net
References: <373698cabe053cb9bec8e1f6dc969906@mail.gmail.com>
Organization: AFUP
Message-ID: <5695F94D.5050808@pascal-martin.fr>
Date: Wed, 13 Jan 2016 08:14:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <373698cabe053cb9bec8e1f6dc969906@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] [RFC] [VOTE] PHP 5's Support Timeline
From: mailing@pascal-martin.fr ("Pascal MARTIN, AFUP")

Le 05/01/2016 10:51, Zeev Suraski a écrit :
> the vote is now
> open for the PHP 5 Support Timeline RFC:
>
> https://wiki.php.net/rfc/php56timeline#vote

Hi,

We've discussed this at length at AFUP, and would be +1 to extend the 
lifetime of PHP 5, by a huge margin.

As for the duration, we would be on the 1+1 year side, by a smaller margin.


Basically:

  - Not everyone will switch to PHP 7 right away, so extending support, 
especially for security, seems necessary.
  - But extending it for too long could give a wrong message to some 
users, like "no need to upgrade"; and we don't want that.
  - Also, after a while, we would prefer time being spent on 7.x instead 
of used maintaining 5.x for years.
  - And, in any case, some users will never upgrade, no matter how long 
5.x is maintained... that's just how it is.


Thanks

-- 
Pascal MARTIN, AFUP - French UG
http://php-internals.afup.org/