Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30637
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.228 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=httXk3aJwWvzr/ftL9rxsWqbq93BGj6B5iwigiJZwUllpyVRXuA2WvDX22KwfT240T9GS54BuM8qIquYQKiCE5PeBr+1/qLD+uHGkFG4LbXWD2T4bFu8RQsOg67rE2o5D6f7LnQzk+LHYHR+9nYJQWO8r7lzQWfrx3cCNR0/u/o=
Message-ID: <7d5a202f0707082329j1104badcp17c4f86c9e09c7c4@mail.gmail.com>
Date: Mon, 9 Jul 2007 02:29:26 -0400
To: internals@lists.php.net
In-Reply-To: <fe05d1540707082228i426340edjacd1f8c3de651943@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <698DE66518E7CA45812BD18E807866CE5A8F68@us-ex1.zend.net>
	 <alpine.DEB.0.98.0707081145520.17366@kossu.ez.no>
	 <4691285E.5020904@keryx.se> <4691438B.4070902@lerdorf.com>
	 <34903.78.61.224.253.1183926344.squirrel@avilys.eik.lt>
	 <b5f7bf6c0707081421m3aac5c43wd45a962078252449@mail.gmail.com>
	 <698DE66518E7CA45812BD18E807866CE5A8FEF@us-ex1.zend.net>
	 <d8269d910707081628l12d40f81q302daf9efdf28632@mail.gmail.com>
	 <698DE66518E7CA45812BD18E807866CE5A8FF5@us-ex1.zend.net>
	 <fe05d1540707082228i426340edjacd1f8c3de651943@mail.gmail.com>
Subject: Re: [PHP-DEV] RIP PHP 4?
From: judas.iscariote@gmail.com ("Cristian Rodriguez")

On 7/9/07, Pierre <pierre.php@gmail.com> wrote:

> That's the ideal world.

Unfortunately yes.


>They should really not use it anymore but they
> can and they will. No matter what we do.

Right.

> Some Linux distributors will certainly
> take care of php5 for an even longer period.

Yes, about 6 or 7 years more.

> It is not really important if it is one year or six months (not like
> php4 gives us a lot of work :), my preference still goes to the end of
> this year. From my point of view, the year is merely a marketing
> argument, if it helps us to get a better image, why not...


IMHO this should be done this way

1. Announce **clearly** that PHP4 has reached EOL ASAP.

2. Stop any kind of non-security bugfixing **inmediately** ( well.
that is happening now anyway, :-) ) This include marking as wont fix
all the opened PHP4 bug reports and removing PHP4 from the version
list in the bugtracker as well adding a warning in the bug report form
about this.

3. Move PHP4 releases to the Museum ASAP.

4. gave users a reasonable time to discontinue security fixes (no less
that 8 months IMHO) also state clearly that this covers only critical
security bugs.

5. Fix the documentation, the migration to PHP5 documents are missing
many backward incompatible changes.

just as an example.

http://php.net/manual/en/migration5.incompatible.php does not list the
fact that you cannot reasign $this and that unset($this) does nothing.
there are many others.

6. finally people will attempt to use backward compatibilty hacks like
the horrendous and non-working like zend.ze1_compatibility_mode, it is
very important to either fix it or remove it ( I suggest removing it)
, there are many extensions that dont even work or crash with it
enabled.

my $2 chilean pesos.