Den 2016-06-16 kl. 18:30, skrev Rowan Collins:
On 16/06/2016 17:24, Levi Morrison wrote:
I also have to say that to the very short timeline to finalize 7.0
should not be paid by breaking BCs in 7.x. We can have a short
timeline for 8.0 as well. If we need more drastic BC breaks earlier
than expected. If JIT is a goal for 8.0, then let do the BC breaks in
8.0 and prepare our users using 7.x.
I agree with sentiment. However I do not mind certain BC breaks being
made in 7.1. For 7.2 and beyond I think we should be significantly
more strict on BC breakages.
Why? What's special about 7.1? If it was a case of finishing off
changes that "should have been part of 7.0", I can see some kind of
logic, but the ones we're actually discussing seem to be more about
"preparing for 8.0".
Regards,
The statement above by Levi makes perfect sense in my eyes and
what makes the early minor releases special after a major release
is that the uptake of 7.x is not so large yet. So running a migration
project from PHP 5.x targeting PHP 7 could go for either 7.0 or 7.1.
Going for later minor releases finding minor BC breaks then requires
another migration project, albeit small.
Regards //Björn Larsson
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
