On 24.08.2017 at 00:06, Adam Baratz wrote: >> That change was implemented in the SQLite3 extension without a RFC, so I'm >> quite confused here. > > My literal reading of the contribution guide[1] is that new features should > be preceded by an RFC, though there are certainly cases where this doesn't > happen. I don't have a clear enough understanding of this community to say > when RFCs can be skipped. I'm not sure who the authority would be. The > release manager for the next minor rev? Anyone with commit privileges?
It seems to me this is rather simple: if a feature is uncontroversial, it doesn't need an RFC. Since nobody objected against PR #2528, it was merged (after some weeks). However, there have been objections against PR #2698, so an RFC appears to be appropriate. -- Christoph M. Becker -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
