Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30542
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.132.244 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:cc:in-reply-to:mime-version:content-type:references;
        b=ZpPGYaAU9iUu2ULoo5G+ippZ9O3SaicbylQF9Lr6uO3s2M25avVgZjV2MCOMmQZ0BQa0QcAUQJhxb5wb+ZfIrCpyD0zfENRE05URkGxsZkVsL/BWwfAP/Oq/PQUGkf6eMoNHSueC2q6YCe4zqQXimROYrGfsKZtsdIQFJ4jnopk=
Message-ID: <261daaa10707061001n4223cd1fwe7b915079c68cabb@mail.gmail.com>
Date: Fri, 6 Jul 2007 20:01:49 +0300
To: "William A. Rowe, Jr." <wrowe@rowe-clan.net>
Cc: Tijnema <tijnema@gmail.com>, "Derick Rethans" <derick@php.net>, 
	"PHP Developers Mailing List" <internals@lists.php.net>
In-Reply-To: <468E72DB.6030903@rowe-clan.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
	boundary="----=_Part_89366_25808121.1183741309965"
References: <alpine.DEB.0.98.0707061625150.11364@kossu.ez.no>
	 <d8269d910707060742r76f29a47sdb6a4eeec3b829cf@mail.gmail.com>
	 <261daaa10707060751i25d3c5f8qee7e5da8de0b99a0@mail.gmail.com>
	 <468E72DB.6030903@rowe-clan.net>
Subject: Re: Stuck on PHP 4?
From: kenashkov@gmail.com ("Vesselin Kenashkov")

------=_Part_89366_25808121.1183741309965
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I agree (this is why wrote "I see (and understand) both the desire of the
developers and the objective reasons..") and I do not want to start this
topic again. The move is inevitable.

But please take a look what Rasmus said:
"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?"

I totally agree with him. So there must be a definition what exactly is
being "dropped" (or actually just a message will be added on the hope page
wihtout policy change?).

And my point in the previous message was that after having php6 released,
there will be at least two reasons - the new version will have obvious
advantages, and as well the new version number will be 6, which
automatically even without announce means that v4 will be phased out. I am
not deep into the php internals and policies, but do you consider direct
php4->php6 migration? Any comments?

But I agree - if you want to speed up the migration - it is a good idea to
place an announcement on the home page like "PHP v4 is being phased out. New
versions will not be released after xx/xx/2007/8 ... "


Vesselin Kenashkov

On 7/6/07, William A. Rowe, Jr. <wrowe@rowe-clan.net> wrote:
>
> Vesselin Kenashkov wrote:
> > -1
> > Because the majority of the installation (somebody two month ago in this
> > list mentioned that php 5 has just 10% adoption) is still php4 just
> > makes no sense to drop the support.
>
> This is a very old and tired argument, and pretty much is exactly where
> Apache httpd was, with respect to 1.3, at a similar timeframe.
>
> Folks find it to easy to stay with what they have installed.  And even
> once 4.4 'ends', you will still have security patches (as mentioned)
> to keep them safe, if they even bother the patch/update.  Adoption will
> be slow.
>
> But it doesn't justify leaving the developers dug in the sands trying
> to move changes back to 4.4.  If they want the glitz, jazz and even the
> most up to date bug fixes, they'll have to come along for the ride.
>
> Take care of your *developers*, and your users will have a platform they
> can appreciate and enjoy.  Focus on acting like a BigCo and you will sap
> the developers' time and energy.
>

------=_Part_89366_25808121.1183741309965--