> > If it fixes a bug, it should be merged before RC 1, > if it's a new feature or behavior change without a good reason, it should > probably put off until PHP 8.3. >
As it was noted by Christoph, this is specifically spelled in release process [1] and it was always the case that we allowed self contained feature to be introduced even in patch releases. I think if you dislake this rule, you should open a general discussion and change that rule first which might require using RFC process. It's true that maybe it's not clear if they apply on the RC versions in which case we would probably need to target lower branches (most likely 8.1) but then it would automatically got to 8.2 anyway. So I think it would be better to just get it to 8.2. In any case the RM should follow our rules so the only question that is unresolved is whether those features qualify as self contained which I think they do. If you don't think that's not the case, please could you specifically state what you think is not self contained about those features or another reason why would you not allow it. >From the user point of view I don't see any reason why it should wait anothe. There is no BC break (at least in the 4 that I proposed) or technical risk. [1] https://wiki.php.net/rfc/releaseprocess#releases_cycle Regards Jakub
