Re: Problems with the fix for the BC break introduced in 5.4.29 and 5.5.13

On Thu, Jun 19, 2014 at 2:04 PM, André Rømcke <andre.romcke@ez.no> wrote: > Travis is now running PHP 5.4.29, tests are failing all over the place > right now*. > When these kind of things happen, just take down the release while you > work out the details please. > > > (* most people in the wild don’t always use latests PHPUnit as it has a > tendency to break stuff badly, just look to the now dead Zeta Components > for a example of bad PHPunit breaks) > > > we can't really "take down" a release after it was announced(it is not a technical limitation, but a logical one, the cat is out of the bag already at that point), our only option is to quickly release another one, but that should be used as a last-resort action, as we have many precedence that releases like that (made under time pressure) are more likely to don't properly fix the problem at hand, or that it introduces another one. as you can see from the discussion above, we are still not sure about whether or not we want to "fix" the behavior change in 5.4.29/5.5.13 so I think it was a good thing that we didn't took down the release and rushed another release, which reverts the behavior when there is a chance that we decide to keep the original fix anyways. (* most people testing their php lib/app on travis probably use the phpunit pre-installed on the travis box, the same as they do with the php install) ps: please don't top post on this list. -- Ferenc Kovács @Tyr43l - http://tyrael.hu