Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:30560 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24393 invoked by uid 1010); 6 Jul 2007 18:46:15 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 24377 invoked from network); 6 Jul 2007 18:46:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Jul 2007 18:46:15 -0000 Authentication-Results: pb1.pair.com smtp.mail=evert@rooftopsolutions.nl; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=evert@rooftopsolutions.nl; sender-id=unknown Received-SPF: error (pb1.pair.com: domain rooftopsolutions.nl from 66.207.192.6 cause and error) X-PHP-List-Original-Sender: evert@rooftopsolutions.nl X-Host-Fingerprint: 66.207.192.6 smtp1.beanfield.net FreeBSD 4.6-4.9 Received: from [66.207.192.6] ([66.207.192.6:4151] helo=smtp1.beanfield.net) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 3F/C1-09628-4FD8E864 for ; Fri, 06 Jul 2007 14:46:13 -0400 Received: from 206-223-184-72.beanfield.net (206-223-184-72.beanfield.net [206.223.184.72]) by smtp1.beanfield.net (8.13.4/8.12.11) with ESMTP id l66Igmdm027768; Fri, 6 Jul 2007 14:42:49 -0400 (EDT) (envelope-from evert@rooftopsolutions.nl) Message-ID: <468E8DBC.50906@rooftopsolutions.nl> Date: Fri, 06 Jul 2007 14:45:16 -0400 User-Agent: Thunderbird 2.0.0.4 (Macintosh/20070604) MIME-Version: 1.0 To: Marco CC: Antony Dovgal , Rasmus Lerdorf , Derick Rethans , PHP Developers Mailing List References: <468E5AB1.3080308@lerdorf.com> <468E5E3B.5090408@zend.com> <2fd662a00707061057n799a83f9h18f306e8e559a6f1@mail.gmail.com> In-Reply-To: <2fd662a00707061057n799a83f9h18f306e8e559a6f1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RIP PHP 4? From: evert@rooftopsolutions.nl (Evert | Rooftop) My 2 cents: Before you guys are making any changes in the maintenance process, I think the end goal (dropping PHP4 support) can happen a lot smoother with good communication. You can start today by stating really clear on www.php.net that PHP4 support is going to be dropped in the future and considered 'old', also to Marco's point .. putting the downloads in the museum site will be a really clear statement even though you don't actually have to drop support for PHP4 till some time in the future.. Reading other people's comments it looks like getting people to switch to PHP5, but also remain faithful and supporting to your community is dear to people. The first step to achieve both is to change your communication, not the actual maintenance process. Evert Marco wrote: > > Also I would suggest removing links to PHP4 downloads away from the front > page on the php.net site and maybe put them onto the museum site? > > Regards > > Marco >