Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38825
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.82.236 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=fCunH7n+JZPSzlTyXTf41X3M5PdoUL9BkTvusjwuHubmQEy967ViHzA9YNy6EmmIss
         uhURXr9WxHDhXAQZ3HukM9Ck/yrohnrLbejBgxsxQvndaNWs1J8fiVKyNH5oiwS+31qj
         1w2R2IyQ+XIKDMW1DEhJ5xN50qP8Z57ZfHQ4o=
Message-ID: <34eeaeca0807070905l10d8698ei9cf4ff5771f1cf67@mail.gmail.com>
Date: Mon, 7 Jul 2008 11:05:08 -0500
To: "PHP Internals" <internals@lists.php.net>
In-Reply-To: <698DE66518E7CA45812BD18E807866CE01C3AB6B@us-ex1.zend.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_10925_23098374.1215446708768"
References: <alpine.DEB.0.98.0807070905100.22423@kossu.ez.no>
	 <7f3ed2c30807070051q706kccf11d9cfbac5efc@mail.gmail.com>
	 <4871D192.6050902@sci.fi>
	 <alpine.DEB.0.98.0807071050320.22423@kossu.ez.no>
	 <353f2c6f0807070415o7a9e083eo8eceaf6f054b8036@mail.gmail.com>
	 <1109578988.20080707150201@marcus-boerger.de>
	 <alpine.DEB.0.98.0807071621180.30645@kossu.ez.no>
	 <698DE66518E7CA45812BD18E807866CE01C3AB6B@us-ex1.zend.net>
Subject: Re: [PHP-DEV] PHP 4.4.9
From: pencap@gmail.com ("Mike Willbanks")

------=_Part_10925_23098374.1215446708768
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hello,

On Mon, Jul 7, 2008 at 9:29 AM, Andi Gutmans <andi@zend.com> wrote:

> > On Mon, 7 Jul 2008, Marcus Boerger wrote:
> >
> > >   Janusz is damn right here. Make the patches available but do not
> > > make it easy for people to stick to 4 please. Instead, stick to th
> > > eplan.
> >
> > We do, there are security fixes - we make a release.
>
> I'm with Derick here. We should push out new releases when there are
> security issues


While I mostly observe here, I would like to add some feedback from this
point of view.  With PHP 4, the date still has not been reached and if there
are security flaws they should be patched and released.  This should not be
sending mixed messages with the end of life announcement.  From the
enterprise perspective, we are out of compliance once the end of life has
been exceeded and internal policies will force many on PHP 4 to upgrade to
PHP 5 once that date has been reached.

Within these environments there might be legacy applications running on PHP
4 that are either waiting to reach their end of cycle or need to be upgraded
and the only way that does happen is when those timelines are reached when
the language reaches the end of it's life cycle.

Mike

------=_Part_10925_23098374.1215446708768--