On 27.06.2018 at 15:00, Jakub Zelenka wrote: > I think it makes sense for big engine changes that you described but I > don't think this should be the case for features in core extensions and > SAPI's. The thing is that some of us are not going to work on those big > changes for various reasons. Personally I work mainly on fpm, openssl as > well as some other stuff and just don't have time to do anything else atm. > My features are not really so big that they should wait 2 years. The thing > is that this type of changes won't usually conflict with engine changes so > there should be no reason to delay it. > > So I think it would be good idea to lock the engine (possibly create a > special branch for all the new changes into it) and release 7.4 and maybe > 7.5 (in case 8.0 is not ready in time) with just deprecations and features > in extensions and SAPI's.
This was my first thought as well, but considering the changes that PHP 7 required for *all* extensions, working on 7.4 and 8.0 simultaneously may easily lead to hard to resolve merge conflicts, and even to subtle breakages. However, instead of locking 7.4 for everything but deprecations in advance, we may consider to decide on a case-by-case basis if a new feature should target 7.4 or 8.0. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
