On Thu, Jun 8, 2017 at 9:52 AM, François Laupretre <franc...@php.net> wrote: > > I am sorry you take it this way. Voting today on a feature for 8.0 > wouldn't be ridiculous and it would make me change my vote, as most others. > Instead of nonsense, it would be a sign of maturity for the PHP project. It > would be great, IMO, to open a 'Approved for 8.0' section on the RFC page > now, and your RFC could proudly be the 1st one to enter it. >
I agree with your suggestion and general sentiment so I propose to do the following: - The current voting widget refers to introducing the change on 7.2. (Will be mentioned on the RFC page) - Add a new voting widget for introducing the change on 8.0. - Extend the voting period for one more week than originally planned until 27/6/2017 18:00 UTC. Additionally, since some people also mentioned the difficulty in detecting this change, if the vote for 8.0 passes, I suggest to introduce a E_DEPRECATED notice where the implicit keys will change. You can see that implementation here: https://github.com/php/php-src/compare/master...pmmaga:negative-array-deprecated Would it make sense to include an extra voting widget for the introduction of the notice? Given that we are on the voting phase I would oppose changing anything by principle, but given that most of the discussion on the topic only started when the vote was started and what is dividing the vote is the timing, I think it makes sense to update the RFC in this case. Let me know what you think. Thanks, Pedro
