> -----Original Message----- > From: Rafael Dohms [mailto:lis...@rafaeldohms.com.br] > Sent: Friday, March 08, 2013 2:52 PM > To: Andi Gutmans > Cc: Anthony Ferrara; Philip Olson; David Soria Parra; PHP internals > Subject: Re: [PHP-DEV] [VOTE] Integrating Zend Optimizer+ into the PHP > distribution > > On Fri, Mar 8, 2013 at 6:55 AM, Andi Gutmans <a...@zend.com> wrote: > > > > > The 62.8% comparison to 60.7% is the most out of touch thing I've read > > on this mailing list in a long time. If you're talking about pure > > feature yay/nay then 94% have given a yay to this "feature". The split > > is the timing. > > > > > Sorry, but math is not liable to what is being measured by a percentage. So to > this point if there is something being done without 2/3 approval, then its wrong.
Rafael, You seem to be a bit misinformed here. RFCs actually do NOT require 2/3 majority by default, it's left for special cases only. The default is 50%+1. See for yourself - https://wiki.php.net/rfc/voting There was a bit of discussion on whether or not including Optimizer+ in PHP is an RFC that falls in the special 2/3 requirement or not. We'll talk about that in a sec, but it's not really important at all as for this particular question - 94%, 66 out of 70 voters, voted in favor. There's absolutely no question that changing PHP's release cycle does *not* require a 2/3 vote. Let's look for a second what the voting RFC has to say about it: ------ === Required Majority === Given that changes to languages (as opposed to changes to apps or even frameworks) are for the most part irreversible - the purpose of the vote is to ensure that there's strong support for the proposed feature. It needs to be clear that there are a lot more people actively supporting the proposal, vs. people actively opposing it. We also need to ensure, as much as possible, that the decision isn't based on some arbitrary circumstances (such as a temporary marginal majority for a certain school of thought). For these reasons, a feature affecting the language itself (new syntax for example) will be considered as 'accepted' if it wins a 2/3 of the votes. Other RFCs require 50% + 1 votes to get 'accepted'. ------ I know the text pretty well, I wrote it, and when I wrote it - I meant what I said. It's there to protect against *changes to the language* which are irreversible. The one thing I regret is that the phrasing around what constitutes 'a feature affecting the language itself' was left a bit vague, but one could definitely argue that language syntax and language behavior are what we're talking about here. Implementation details, release timelines, included or excluded extensions - are most certainly not. There's nothing irreversible about them. Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
