Hi,
One month ago, I sent a message (https://marc.info/?l=php-internals
https://marc.info/?l=php-internals&m=142449701107797 &m=142449701107797)
explaining in details why I thought we should take more time to gather
features for 7.0. Zeev replied that it was absolutely impossible, and that
the timeline had to be respected.
Now, after more calls from many of you to delay it, and as Zeev himself
seemed to consider it as more acceptable, I am proposing again to delay 7.0
feature freeze to May, 15 (2 month delay, date where vote is starting). I
wont repeat all the arguments of my previous posts but, to summarize, it
would allow to include important features, making it a real major version.
Releasing a major version is not just a question of BC break, we also need
to think about what we put forward. So, we need features. We already have
STH, but we can do more (I personally have at least 4 RFCs I didnt have
time for, including scalar pseudo-methods, which can be an important
feature).
@Anthony, dont get me wrong, it is absolutely not a way to keep competing
about STH. Your RFC is accepted, thats fine, the debate is over. If we
decide for an additional delay, I may propose something about STH, but it
will be a follow-up to your RFC, proposing additions, not an alternative STH
system.
So, Zeev asked in a previous mail how we could decide to delay the timeline,
as it would theoretically require an RFC, which would take all the time.
Good question. But, as I have a feeling that everyone except Zeev was quite
flexible on the question, maybe we can have an agreement without organizing
a formal vote.
Just a proposal, give thoughts.
Regards
François
Now, after more calls from many of you to delay it, and as Zeev himself
seemed to consider it as more acceptable, I am proposing again to delay 7.0
feature freeze to May, 15 (2 month delay, date where vote is starting). I
won’t repeat all the arguments of my previous posts but, to summarize, it
would allow to include important features, making it a ‘real’ major version.
Releasing a major version is not just a question of BC break, we also need
to think about what we put forward. So, we need features. We already have
STH, but we can do more (I personally have at least 4 RFCs I didn’t have
time for, including scalar pseudo-methods, which can be an important
feature).
No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely. And I
completely disagree that this isn't a 'real' major version.
-Rasmus
Sent from my mobile
Now, after more calls from many of you to delay it, and as Zeev himself
seemed to consider it as more acceptable, I am proposing again to delay 7.0
feature freeze to May, 15 (2 month delay, date where vote is starting). I
won’t repeat all the arguments of my previous posts but, to summarize, it
would allow to include important features, making it a ‘real’ major version.
Releasing a major version is not just a question of BC break, we also need
to think about what we put forward. So, we need features. We already have
STH, but we can do more (I personally have at least 4 RFCs I didn’t have
time for, including scalar pseudo-methods, which can be an important
feature).No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely. And I
completely disagree that this isn't a 'real' major version.
+1
Zeev
Sent from my mobile
Now, after more calls from many of you to delay it, and as Zeev himself
seemed to consider it as more acceptable, I am proposing again to
delay 7.0
feature freeze to May, 15 (2 month delay, date where vote is
starting). I
won’t repeat all the arguments of my previous posts but, to summarize,
it
would allow to include important features, making it a ‘real’ major
version.
Releasing a major version is not just a question of BC break, we also
need
to think about what we put forward. So, we need features. We already
have
STH, but we can do more (I personally have at least 4 RFCs I didn’t
have
time for, including scalar pseudo-methods, which can be an important
feature).No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely. And I
completely disagree that this isn't a 'real' major version.+1
Same.
Zeev
Le Sat, 21 Mar 2015 18:44:23 +0100, Pierre Joye pierre.php@gmail.com a
écrit:
Sent from my mobile
Now, after more calls from many of you to delay it, and as Zeev
himself
seemed to consider it as more acceptable, I am proposing again to
delay 7.0
feature freeze to May, 15 (2 month delay, date where vote is
starting). I
won’t repeat all the arguments of my previous posts but, to
summarize,
it
would allow to include important features, making it a ‘real’ major
version.
Releasing a major version is not just a question of BC break, we also
need
to think about what we put forward. So, we need features. We already
have
STH, but we can do more (I personally have at least 4 RFCs I didn’t
have
time for, including scalar pseudo-methods, which can be an important
feature).No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely.
And I
completely disagree that this isn't a 'real' major version.+1
Same.
Zeev
Same here, very bad idea
Please do not delay. Any one remember PHP 6 ?
Delay is bad smell. means the project will failure.
PHP 7 already had much more features. That's fine .
Just ship it .
Appreciate your time.
Netroby
2015-03-22 4:09 GMT+08:00 Benoit Schildknecht bensor987@neuf.fr:
Le Sat, 21 Mar 2015 18:44:23 +0100, Pierre Joye pierre.php@gmail.com a
écrit:Sent from my mobile
Now, after more calls from many of you to delay it, and as Zeev
himself
seemed to consider it as more acceptable, I am proposing again todelay 7.0
feature freeze to May, 15 (2 month delay, date where vote is
starting). I
won’t repeat all the arguments of my previous posts but, to summarize,
it
would allow to include important features, making it a ‘real’ major
version.
Releasing a major version is not just a question of BC break, we also
need
to think about what we put forward. So, we need features. We already
have
STH, but we can do more (I personally have at least 4 RFCs I didn’t
have
time for, including scalar pseudo-methods, which can be an important
feature).No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely. And
I
completely disagree that this isn't a 'real' major version.+1
Same.
Zeev
Same here, very bad idea
OK. It was just a suggestion. Forget it. Thanks for your time.
-----Message d'origine-----
De : Netroby [mailto:hufeng1987@gmail.com]
Envoyé : dimanche 22 mars 2015 01:21
À : Benoit Schildknecht
Cc : PHP Internals
Objet : Re: [PHP-DEV] Proposal to delay 7.0 timelinePlease do not delay. Any one remember PHP 6 ?
Delay is bad smell. means the project will failure.
PHP 7 already had much more features. That's fine .
Just ship it .Appreciate your time.
Netroby
2015-03-22 4:09 GMT+08:00 Benoit Schildknecht bensor987@neuf.fr:
Le Sat, 21 Mar 2015 18:44:23 +0100, Pierre Joye pierre.php@gmail.com a
écrit:Sent from my mobile
On 21 במרץ 2015, at 18:05, Rasmus Lerdorf rasmus@lerdorf.com
wrote:Now, after more calls from many of you to delay it, and as Zeev
himself
seemed to consider it as more acceptable, I am proposing again todelay 7.0
feature freeze to May, 15 (2 month delay, date where vote is
starting). I
won’t repeat all the arguments of my previous posts but, to
summarize,it
would allow to include important features, making it a ‘real’ major
version.
Releasing a major version is not just a question of BC break, we also
need
to think about what we put forward. So, we need features. We
alreadyhave
STH, but we can do more (I personally have at least 4 RFCs I didn’t
have
time for, including scalar pseudo-methods, which can be an important
feature).No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely. And
I
completely disagree that this isn't a 'real' major version.+1
Same.
Zeev
Same here, very bad idea
Now, after more calls from many of you to delay it, and as Zeev himself
seemed to consider it as more acceptable, I am proposing again to delay 7.0
feature freeze to May, 15 (2 month delay, date where vote is starting). I
won’t repeat all the arguments of my previous posts but, to summarize, it
would allow to include important features, making it a ‘real’ major version.
Releasing a major version is not just a question of BC break, we also need
to think about what we put forward. So, we need features. We already have
STH, but we can do more (I personally have at least 4 RFCs I didn’t have
time for, including scalar pseudo-methods, which can be an important
feature).No, please, let's get what we have stabilized and out the door. There
are always more things to do and we can delay things indefinitely. And I
completely disagree that this isn't a 'real' major version.-Rasmus
+1
So, we need features. We already have
STH, but we can do more (I personally have at least 4 RFCs I didn’t have
time for, including scalar pseudo-methods, which can be an important
feature).
We add scalar and return types in PHP 7.0. We also add null coalesce
?? and three-way comparison operator <=>. All-in-all, we have good
features already. I don't see why we need to post-pone PHP 7.0 for
more features.