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 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
