Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30573
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.166.181 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:disposition-notification-to:date:from:user-agent:to:subject:references:in-reply-to:mime-version:content-type;
        b=IJ1CDOXuOc2r5CIrFYBPgfDYo/l8ccn7fo8K0xhdznWVahAtp1uXWdOSFG7+M39fpVFR4IZFE3ugdJX+9VfOsLfEzs8Dwa7Wxako0j8CBmo14QDuLNPbUCbG6m47U8k+xKqKyGO8r3uapu8e1P45r7HnLaEbDV8Oc4VblmI9bQQ=
Message-ID: <468EC163.9080805@gmail.com>
Disposition-Notification-To: "Anton C. Swartz IV" <djnecrogami@gmail.com>
Date: Fri, 06 Jul 2007 18:25:39 -0400
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
To: Derick Rethans <derick@php.net>, 
 PHP Developers Mailing List <internals@lists.php.net>
References: <alpine.DEB.0.98.0707061625150.11364@kossu.ez.no> <468E5AB1.3080308@lerdorf.com> <alpine.DEB.0.98.0707061933470.11364@kossu.ez.no>
In-Reply-To: <alpine.DEB.0.98.0707061933470.11364@kossu.ez.no>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=------------060609090404020404060104
Subject: Re: [PHP-DEV] RIP PHP 4?
From: djnecrogami@gmail.com ("Anton C. Swartz IV")

--------------060609090404020404060104
Content-Type: multipart/alternative; boundary=------------000403000500080006020709

--------------000403000500080006020709
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

+1
---
Anton C. Swartz IV
Phoenix Edge Network L.L.C. - *Owner*
PHPLogic Development Services – *Co-Owner*
_Based in Indianapolis, IN_

"The Opposite of war is not Peace it is Creation."

Don't let sin rule your body. After all, your body is bound to die, so 
dont obey its desires or let any part of it become slave to evil. Give 
yourselves to God, as people who have been raised from death to life. 
Make every part of your body a slavethat pleases God. Don't let sin keep 
ruling your lives.You are ruled by God's Kindness and not by the law.
_Romans 6:12-14_


Derick Rethans wrote:
> On Fri, 6 Jul 2007, Rasmus Lerdorf wrote:
>
>   
>> Derick Rethans wrote:
>>     
>>> Ladies, Gentlemen, Kings and Princesses,
>>>
>>> With the nice PHP 5 / PHP 6 unicode semantics thread under way I am 
>>> trying to gauge what people feel about dropping support for PHP 4 at the 
>>> end of this year. That does not mean that we will not fix security 
>>> issues, we have to as the install base is too large, but that would be 
>>> the only thing that would warrant a new release. I already sort of 
>>> mentioned this on april 1st, but I think we should come with a slightly 
>>> more official statement. Your votes please (only -1 and +1 are 
>>> allowed)!
>>>       
>> I'm breaking your vote only rule.  I don't really understand what
>> dropping support means if we will still release security fixes.  That's
>> the mode we have been in for at least a year, so what would change at
>> the end of the year?
>>     
>
> Actually, that's not the current mode. Normal bug fixes are backported 
> as well at this moment. Dropping support would mean that we won't do 
> that anymore.
>
>   
>> Dropping support to me means PHP 4 becomes like PHP 3.  No new releases
>> for any reason, and I don't think we can realistically do that yet.
>> Saying we are dropping support and then continuing on with the status
>> quo seems odd to me.
>>     
>
> Besides it not being totally the same, I think that giving out a 
> statement "No more bug fixes after 2007-12-31" and "No more security 
> fixes after 2008-08-08" gives a *very* clear statement that it's the end 
> for PHP 4. That will perhaps drive the increase of PHP 5.2 support, and 
> that should be our main goal as we can not keep supporting PHP 4 for 
> ever.
>
> regards,
> Derick
>
>   

--------------000403000500080006020709
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
+1<br>
---<br>
<div class="moz-signature">
<title>Anton C. Swartz IV Signature</title>
<font color="#ff6600">Anton C. Swartz I</font><font color="#ff6600">V</font><br>
Phoenix Edge Network L.L.C. - <b>Owner</b><br>
PHPLogic Development Services – <b>Co-Owner</b><br>
<u>Based in Indianapolis, IN</u><br>
<br>
<font color="#009900">"The Opposite of war is not Peace it is Creation."</font><br>
<br>
<font color="#0000ff">Don't let sin rule your body. After all, your
body is bound to die, so dont obey its desires or let any part of it
become slave to evil. Give yourselves to God, as people who have been
raised from death to life. Make every part of your body a slavethat
pleases God. Don't let sin keep ruling your lives.You are ruled by
God's Kindness and not by the law.<br>
<u>Romans 6:12-14</u></font>
</div>
<br>
<br>
Derick Rethans wrote:
<blockquote cite="mid:alpine.DEB.0.98.0707061933470.11364@kossu.ez.no"
 type="cite">
  <pre wrap="">On Fri, 6 Jul 2007, Rasmus Lerdorf wrote:

  </pre>
  <blockquote type="cite">
    <pre wrap="">Derick Rethans wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">Ladies, Gentlemen, Kings and Princesses,

With the nice PHP 5 / PHP 6 unicode semantics thread under way I am 
trying to gauge what people feel about dropping support for PHP 4 at the 
end of this year. That does not mean that we will not fix security 
issues, we have to as the install base is too large, but that would be 
the only thing that would warrant a new release. I already sort of 
mentioned this on april 1st, but I think we should come with a slightly 
more official statement. Your votes please (only -1 and +1 are 
allowed)!
      </pre>
    </blockquote>
    <pre wrap="">I'm breaking your vote only rule.  I don't really understand what
dropping support means if we will still release security fixes.  That's
the mode we have been in for at least a year, so what would change at
the end of the year?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Actually, that's not the current mode. Normal bug fixes are backported 
as well at this moment. Dropping support would mean that we won't do 
that anymore.

  </pre>
  <blockquote type="cite">
    <pre wrap="">Dropping support to me means PHP 4 becomes like PHP 3.  No new releases
for any reason, and I don't think we can realistically do that yet.
Saying we are dropping support and then continuing on with the status
quo seems odd to me.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Besides it not being totally the same, I think that giving out a 
statement "No more bug fixes after 2007-12-31" and "No more security 
fixes after 2008-08-08" gives a *very* clear statement that it's the end 
for PHP 4. That will perhaps drive the increase of PHP 5.2 support, and 
that should be our main goal as we can not keep supporting PHP 4 for 
ever.

regards,
Derick

  </pre>
</blockquote>
</body>
</html>

--------------000403000500080006020709--
--------------060609090404020404060104
Content-Type: text/plain; x-avg=cert; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Description: "AVG certification"

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.476 / Virus Database: 269.10.1/888 - Release Date: 7/6/2007 6:3=
6 AM

--------------060609090404020404060104--