Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76075
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain litespeedtech.com designates 209.85.216.48 as permitted sender)
Message-ID: <53D18775.3020107@litespeedtech.com>
Date: Thu, 24 Jul 2014 18:23:49 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?= <johannes@php.net>
CC: internals@lists.php.net
References: <539B8B74.6030707@sugarcrm.com> <53CB0347.2030902@sugarcrm.com>	 <53CEB32B.8030407@sugarcrm.com>  <53D03599.20205@litespeedtech.com> <1406212844.3964.140.camel@guybrush>
In-Reply-To: <1406212844.3964.140.camel@guybrush>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Re: 5.3 final release
From: gwang@litespeedtech.com (George Wang)


On 7/24/2014 10:40 AM, Johannes Schlüter wrote:
> On Wed, 2014-07-23 at 18:22 -0400, George Wang wrote:
>> Hi,
>>
>> I have a request to include our latest sapi/litespeed V6.6 to the EOL
>> PHP 5.3 release. I thought it was EOL already.
> PHP 5.3 is in extended support and only receives security related fixes.
> In general people should use newer versions which have more bug fixes
> and are faster.
> I don't think these updates qualify.
>
>> We had some difficult to commit our LiteSpeed SAPI code into PHP
>> source repository before, so it is lagging behind our office release.
> What kind of issues?
A while back, I can only push change to master branch, but cannot push 
to other branches.
So, master was updated to V6.4 last year, but other branches still stay 
at V5.5, which was released 4 years ago.

I can push changes to other branches without problem now, all up2date 
now except the 5.3 branch.

Best regards,
George