Hi! > I am sorry for the contributor but my example is > https://github.com/php/php-src/pull/1145 > (DateTime::createFromImmutable() method) which was posted here on the > list, got three negative replies but was merged nevertheless. I will not > reproduce the arguments here but now the door for a clean solution > inside the DateTimeInterface seems closed forever.
Why is it closed forever? I've seen Derick look at the patch and didn't see any objection from him except for small CS fixes. Also, we did not release it yet so if there's any problem with it it still can be reverted. But I haven't seen any mention of it so far on the list except for this mention in completely unrelated topic which would be extremely easy to miss and that says basically "all is lost now, no use to discuss it, the end is nigh" without explaining anything. If you want to explain yourself, please start a topic and do this, we have 2 weeks before 5.6.8, ample time to revert if necessary. > Besides, I think that the vast majority of PHP users out there is using > distro versions, so it does not matter to them if a feature goes into > 5.6.7 oder 7.1.0, they will get the feature when the distro upgrades. That'd basically mean "never", no distro would go from 5.6 to 7.1 within the same version, and changing distro version is insanely operationally complex thing which is done very rarely. > So, please let the x.y.z versions contain only additional (security) > fixes and stick to the RFC process, thanks. We are already doing this. The discussion is about changing the process to ban enhancements in released versions, which was never the case and we specifically emphasized this when we started it. Now you seem to propose to ban non-security bugfixes on releases too. So basically you'd have to wait for years to even get a bug fixed. Nice. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
