Re: PHP 5.5 Upgrade Notes Question
| From: | Pierre Joye | Date: | Fri, 22 Mar 2013 06:34:09 +0000 |
| Subject: | Re: PHP 5.5 Upgrade Notes Question | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-66744@lists.php.net to get a copy of this message | ||
hi,
On Fri, Mar 22, 2013 at 6:18 AM, Andi Gutmans <andi@zend.com> wrote:
> Some questions:
>
> - Dropped support for Windows XP & 2003:
>
> o Was this an RFC? At what point was it decided? (I may have missed it in
> that case I’d just appreciate a pointer to where it was decided). I am
> asking because XP still seems to be quite prevalent and while Microsoft
> wants to incentivize people to upgrade by being aggressive around end of
> life, not sure that’s the most convenient for our users.
It was announced with 5.4.0, 5.4.0 was the last release to support
Windows XP/2003. Which were already not supported anymore back then.
> - 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.
Sounds good, also if they are internals changes, they should be part
of UPGRADING.INTERNALS, which cruelly needs love:
https://github.com/php/php-src/blob/master/UPGRADING.INTERNALS
> - 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 :)
Sounds good too, however I have to check which BC changes are in
there, as we are not supposed to allow any :) (except bugs fixes for
bad/undocumented/random behavior as usual).
Cheers,
--
Pierre
@pierrejoye