Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:89709 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 29627 invoked from network); 7 Dec 2015 14:33:43 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2015 14:33:43 -0000 Authentication-Results: pb1.pair.com header.from=addw@phcomp.co.uk; sender-id=permerror Authentication-Results: pb1.pair.com smtp.mail=addw@phcomp.co.uk; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain phcomp.co.uk designates 78.32.209.33 as permitted sender) X-PHP-List-Original-Sender: addw@phcomp.co.uk X-Host-Fingerprint: 78.32.209.33 freshmint.phcomp.co.uk Received: from [78.32.209.33] ([78.32.209.33:50074] helo=mint.phcomp.co.uk) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 09/20-28320-2C895665 for ; Mon, 07 Dec 2015 09:33:41 -0500 Received: from addw by mint.phcomp.co.uk with local (Exim 4.72) (envelope-from ) id 1a5wr8-0001aM-Pa for internals@lists.php.net; Mon, 07 Dec 2015 14:33:34 +0000 Date: Mon, 7 Dec 2015 14:33:34 +0000 To: internals@lists.php.net Message-ID: <20151207143334.GA3805@phcomp.co.uk> Mail-Followup-To: internals@lists.php.net References: <566485DD.7010504@garfieldtech.com> <012901d1305d$aa68ed30$ff3ac790$@belski.net> <1B431280-0C1A-4426-8F9E-C07F3ECA773F@heroku.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Organization: Parliament Hill Computers Ltd User-Agent: Mutt/1.5.20 (2009-12-10) Subject: Re: [PHP-DEV] PHP 5.6 life cycle From: addw@phcomp.co.uk (Alain Williams) On Mon, Dec 07, 2015 at 12:17:55PM +0200, Arvids Godjuks wrote: > Hello internals, > > In my opinion, right now what dictates the timeframes is Release Process > RFC: https://wiki.php.net/rfc/releaseprocess > It clearly states the rules of how things are done. > If dates for the PHP 5.6 are to be adjusted, than it requires an RFC > process and should be an exception, not the rule. > > But, for what it's worth - it's fine as it is. Distros will support 5.6 as > long as they need, you can always download older versions for Windows from > php.net archive and so on. It still has almost 2 years in security fixes > left, and that's more than enough time for people to make a move. Others > will just not care to do that anyway for whatever reasons, and nothing can > be done about it. We need to be aware that there are 3 types of user: 1) those who run PHP on a machine provided by their ISP 2) those who run their machine using software that comes ''with the operating system'', I am thinking of Linux users, mainly: RedHat, Debian, SUSE 3) those who are happy & able to upgrade their machine to the something reasonably recent. Those who I want to talk about are (2), they want to have their systems kept up to date by running a daily cron job (yum update, or apt-get ...). We cannot rely on these systems being rebuilt, some have very long lifetimes, eg RedHat/CentOS 7 will be supported until 2024 - and by default runs PHP 5.4 We need to persuade the distros to have PHP 7 available *in addition* to whatever PHP 5.x they have. However: they will probably continue to support PHP 5.x until that version of their OS is EOLed -- which is work that they will have to do. PHP 5.x will still be in use for many years: people put a machine together to do something and then don't want to fiddle with it (which might break applications) for as long as possible. But also they, naturally, want bug fixes. -- Alain Williams Linux/GNU Consultant - Mail systems, Web sites, Networking, Programmer, IT Lecturer. +44 (0) 787 668 0256 http://www.phcomp.co.uk/ Parliament Hill Computers Ltd. Registration Information: http://www.phcomp.co.uk/contact.php #include