Re: BC break in 5.4.29 and 5.5.13
| From: | Rafael Dohms | Date: | Tue, 17 Jun 2014 09:01:19 +0000 |
| Subject: | Re: BC break in 5.4.29 and 5.5.13 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-74933@lists.php.net to get a copy of this message | ||
On Fri, Jun 13, 2014 at 4:25 PM, Marco Pivetta <ocramius@gmail.com> wrote:
> On 13 June 2014 16:19, Remi Collet <remi@fedoraproject.org> wrote:
>
> > See my proposal
> >
> > http://marc.info/?l=php-internals&m=140257374715698&w=2
> >
> > Not designed as a fix, but rather a small improvement to make this hack
> > possible for Internal and Serializable classes
> >
>
> Thanks Remi, that looks indeed like what we'd want :-)
>
> Marco Pivetta
>
> http://twitter.com/Ocramius
>
> http://ocramius.github.com/
>
Its a BC break people.
It does not matter if we think A or B are correct, a point release CANNOT
break BC.
It has been 18 days without a 5.5.14 release or a rollback of 5.5.13.
This is highly unacceptable and irresponsible of a core language.
I cannot understand why we are discussing this and leaving userland broken,
this affect a lot more the phpunit/doctrine.
Rollback the release, or release a 5.5.14 release that fixes it, THEN you
discuss what the proper thing should be and worry about it in 5.5.15.
--
Rafael Dohms
PHP Evangelist and Community Leader
http://doh.ms
http://www.amsterdamphp.nl <http://wwwamsterdamphp.nl>