Hi! >> As you may have noticed if you had a look at the RFC or twitter, I have >> decided to follow people's suggestion. >> Please note that the switch from E_DEPRECATED to fatal error won't require >> any new RFC/discussion/vote >> as the fatal error is considered as approved. I just introduce an >> E_DEPRECATED phase for 7.0. > > What. The. Fuck.
Let's tone down here. While editing RFC anytime after the vote has started without advanced notice is unacceptable and should not be done, I don't think it's anything but a honest mistake. Of course, even more unacceptable is to change it when voting results are in. But let's not create more drama of it then necessary. Wikipedia has a rule that says "assume good faith" (yes, I know in practice it is more complicated :) - I think we could use more invocation of this rule here too. It looks like the RFC author has not really decided what he wants to do. If he doesn't want to support the RFC anymore, as voted, he can just withdraw it and let somebody pick it up if willing (that's what happened to <=> RFC and scalar typing RFC, so we have precedents). Or create a new different one to supersede the old one. What not should be done of course is editing voted RFC and using that as a base for changes. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
