On Jan 19, 2015 12:13 AM, "Nikita Popov" <nikita....@gmail.com> wrote: > > On Sun, Jan 18, 2015 at 6:02 PM, Pierre Joye <pierre....@gmail.com> wrote: >> >> On Sun, Jan 18, 2015 at 11:27 PM, Juan Basso <jrba...@gmail.com> wrote: >> > During the discussion process it was discussed and people were ok with it >> > since it doesn't break any existing code. Also, JSON_NUMERIC_CHECK option >> > was added on json_encode in patch version (added on 5.3.3). >> >> >> I do not know who are the "people" but the release process is pretty >> clear on that. We decided not to allow features additions to ease >> developers life, like not having to do dozen of tests to know which >> minor versions added what. It is also why we have yearly releases, >> reduce the delay between accepted features and actual availability in >> a release. >> >> Please not that the release process was approved after 5.3 and applied to 5.4+. > > > The release process RFC *explicitly* allows the addition of self-contained features in patch releases. This rule is implemented in practice either by RM approval for the feature or an RFC, the latter being the case here.
Except that this one is not self contained and the rfc says in rare cases (or say, for good reason). I give up to try explain where the constant lack of respect of the RFC will lead. That's why I won't battle for this now.
