On Wed, Jun 27, 2018 at 2:10 PM, Christoph M. Becker <cmbecke...@gmx.de> wrote:
> 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. > > Well it was mainly about changing the zval but I guess it won't be the same for 8.0 unless there are some plans for big breaking changes. It would probably make sense to reconsider in that case but if the ABI stays the same or the changes are minimal, then it shouldn't block new features to the extensions IMO. In terms of SAPI's like FPM, it's a bit different as it is mostly independent code and most of the features can be released without any conflict even if the engine ABI changes considerably. Cheers Jakub
