Stas, The issue is that changes were made once the voting started, and some of us were waiting for the vote to restart:
> I'd like to see the vote re-run (1 week?) with the changes in place. I didn't vote because I expected it to be restarted. I would have voted -1 on the current proposal. Changing the RFC during voting requires a _restart_ not an extension. The vote must be re-run. I will not put this in 7.1 without a new vote. - Davey On Sat, Jul 23, 2016 at 12:50 PM, Stanislav Malyshev <smalys...@gmail.com> wrote: > Hi! > > > We already had a vote, at it was completed. Having another vote on the > > same subject, slightly modified, is highly irregular and contrary to > > voting RFC, which mandates 6 month period or *substantial* changes (with > > assumed new discussion period I imagine, since past discussion can't > > really count for substantially changed proposal) to schedule a new vote > > on a rejected proposal. > > > > This also gives pretty bad example - on failed vote, tweak a little > > issue and issue immediate revote, repeat until one of the votes > > succeeds. I understand that this is not at all your intent here, but > > it's the pattern that we do not want to enable. > > > > I voted yes for it, and it is a pity that it failed, as it seems, > > because of a miscommunication (maybe not, I don't know), but going > > against our own agreed process I think is not a good outcome either. > > Oops, I thought I was talking about another RFC vote that failed. Sorry > for the confusion. This one seems to have succeeded. This is weirder > case then... I'd say just implement the uncontroversial part then and > submit the controversial part as a new RFC? > > -- > Stas Malyshev > smalys...@gmail.com > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php >
