Deadline for 7.0; was: [RFC][Discussion] In Operator

9 years ago by Adam Harvey — view source

unread

Question: The timline says "Line up any remaining RFCs that target PHP
7.0.", does that mean RFCs have to
start voting on Mar 15 or should the vote end there?

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.

Thoughts, fellow Internaleers?

Adam

9 years ago by francois@php.net — view source

unread

Hi Adam,

I would say that vote can startby 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.

Regards

François

-----Message d'origine-----
De : adam@adamharvey.name [mailto:adam@adamharvey.name] De la part
de Adam Harvey
Envoyé : vendredi 20 février 2015 19:29
À : Niklas Keller
Cc : PHP Internals
Objet : [PHP-DEV] Deadline for 7.0; was: [RFC][Discussion] In Operator

Question: The timline says "Line up any remaining RFCs that target PHP
7.0.", does that mean RFCs have to
start voting on Mar 15 or should the vote end there?

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.

Thoughts, fellow Internaleers?

Adam

9 years ago by Adam Harvey — view source

unread

(Please don't top post!)

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 startby 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

9 years ago by Yasuo Ohgaki — view source

unread

Hi all,

Question: The timline says "Line up any remaining RFCs that target PHP
7.0.", does that mean RFCs have to
start voting on Mar 15 or should the vote end there?

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 think we had discussion about self contained RFC that will not affect
other parts. Self contained RFC like adding new function that does not
affects others is allowed.

Am I correct?

Regards,

P.S. Since your RFC is language modification, it's not a self contained RFC.

--
Yasuo Ohgaki
yohgaki@ohgaki.net