Re: Deadline for 7.0; was: [RFC][Discussion] In Operator
| From: | Adam Harvey | Date: | Fri, 20 Feb 2015 19:43:13 +0000 |
| Subject: | Re: Deadline for 7.0; was: [RFC][Discussion] In Operator | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-83350@lists.php.net to get a copy of this message | ||
(Please don't top post!)
On 20 February 2015 at 11:31, François Laupretre <francois@php.net> wrote:
>> My interpretation was that votes had to be concluded on or before
>> March 15 to be included in 7.0, but that is kind of ambiguous, now you
>> mention it.
>
> I would say that vote can *start*by March 15, as RFC is not supposed to evolve after vote
> starts, hence 'feature freeze', but I have a personal interest there because it would
> allow to vote on STH after people have enough time to compare concurrent proposals, if there are.
> Otherwise, any work on alternate proposal(s) can stop now, as it is too late to compete.
Just to be clear: if voting has to be finished by March 15, then
working backwards, the last date a new RFC can be submitted is this
Sunday:
- RFC discussion period starts: February 22
- RFC discussion period ends: March 8 (given the minimum of 2 weeks)
- RFC voting period starts: March 8
- RFC voting period ends: March 15 (given the minimum of 1 week)
Obviously those dates get shifted forward a week (so the last date for
a new RFC is March 1) if it's just that voting has to start by the
15th.
Would welcome other thoughts.
Adam