Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:50417
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.183 as permitted sender)
Message-ID: <4CEB1A61.1020202@sugarcrm.com>
Date: Mon, 22 Nov 2010 17:35:29 -0800
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: Felipe Pena <felipensp@gmail.com>
CC: internals <internals@lists.php.net>
References: <AANLkTi=coWEEMNnr_SsTCo7HaXUPRwcJg7fUz=NjA8nq@mail.gmail.com>
In-Reply-To: <AANLkTi=coWEEMNnr_SsTCo7HaXUPRwcJg7fUz=NjA8nq@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Hold off 5.4
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> Given the current state of trunk, I think 5.4 release process should
> not begin tomorrow (alpha or whatever other status). There are
> numerous identified issues that we need to fix before even think to
> begin with a release. For example:

I agree that it's better to discuss RC process RFC before starting the 
actual RC process.

> - There are many changes not BC with 5.x, as we allowed them for the
> development tree, before 5.4 was even a topic

Do you have a list of such changes?

> - APC is not yet bundled. Having the opcode bundle can raise issues by
> one or another, we should have it in from the very 1st release

This can be done post-alpha, I think - it's not very important for the 
rest of the alpha, if there's a problem we can postpone it but I don't 
believe we should hold releases just for that (I do believe we should 
for other things though :)
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227