RE: [PHP-DEV] What's our official stance on small self-contained additions in a micro version

From: Date: Thu, 02 Apr 2015 16:23:07 +0000
Subject: RE: [PHP-DEV] What's our official stance on small self-contained additions in a micro version
References: 1 2 3 4 5 6 7 8 9  Groups: php.internals 
Request: Send a blank email to internals+get-85688@lists.php.net to get a copy of this message
> De : Stanislav Malyshev [mailto:smalyshev@gmail.com] > > > The questions here are: > > * will this code break any code running with PHP before that patch? > > * does this code change the language in any way? > > OK, so I think there's a misunderstanding here. What you describing is > exactly my position - enhancements that are a) small and b) > self-contained are OK, others are not OK. This has been the case since > we started the whole format release process thing. It seems to me we are mixing two questions : can 'small self-contained' changes be introduced in a patch release, and how 'small' and 'self-contained' a change must be not to require an RFC ? It seems implicit that, once an RFC is written, it is not a 'small self-contained' change anymore. One example : https://wiki.php.net/rfc/cyclic-replace can probably be considered as a 'small self-contained' addition. Should I continue with the RFC, respecting feature freeze and proposing it for 7.1, or should I just ask the PR to be merged in 7.0 ? If it is accepted by a vote, can it still go to 7.0 ? It is really not clear to me. Regards François

« previous php.internals (#85688) next »