Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:66745
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.147 as permitted sender)
Message-ID: <514BFD73.2090503@sugarcrm.com>
Date: Thu, 21 Mar 2013 23:42:59 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: Andi Gutmans <andi@zend.com>
CC: "internals@lists.php.net" <internals@lists.php.net>
References: <88c7d143620e5d9a32041b04d5c949bc@mail.gmail.com>
In-Reply-To: <88c7d143620e5d9a32041b04d5c949bc@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] PHP 5.5 Upgrade Notes Question
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

> -          In “Backwards Incompatible Changes” there’s a big list of BC
> changes that are internals and don’t impact user land. So could come across
> a lot more intimidating than it is. I think we should move towards the end
> of the upgrade notes in a section of its own that’s “PHP Internals Changes
> – does not impact user space” (or something of that sort). I’m happy to
> make that change but wanted to bring it up before tackling it.

Definitely should be moved to UPGRADING.INTERNALS - all after "Removal
of Logo GUIDs".

> -          On similar note as previous item, should we put New Features
> before BC changes? No big deal but it’s always nice to have the more
> positive piece first :)

I know I'd look into BC stuff first, because that's the more scary part
of the upgrade. But either way is fine :)

-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227