On the road to PHP 5.7 , or not ?
| From: | Julien Pauli | Date: | Fri, 12 Dec 2014 13:45:23 +0000 |
| Subject: | On the road to PHP 5.7 , or not ? | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-79594@lists.php.net to get a copy of this message | ||
Hi people.
Ferenc and I, actual RM of 5.5 and 5.6 , were discussing the calendar today
on IRC.
Let's start with facts :
- We release new PHP versions (major or minor) on summer. Usually, if we
can have it end of June, it is good.
- We may delay that, 5.6 got released end of summer : in september. It is
bad, but acceptable.
- We always have, from our release process, *2 active versions at the same
time + 1 sec fix version*. Not more, not less.
If we release during summer, that means we need to prepare everything
around Christmas.
Tip : Christmax is approaching :-)
So the main question is : *What version will we release next year ?*
Will we have a PHP 5.7, or jump directly to a 7.0 ?
Don't forget, that if we go for a 5.7 , then we won't have a 7.0 at least
one year later.
If not : we'll happen having 3 active versions (5.6 , 5.7 and 7.0) and one
sec-fix only (5.5) , *this is something we don't want* , because we have
the feeling that it is too much pain to maintain so many versions alive.
- If we go for 7.0 :
I wouldn't mind delaying its release to November(2015) if needed, its a
major, extra care should be taken. However, not later : our release process
status for 2 years of active life , if 7.0 were to be released in 2016,
then we'd have 5.5 lasting for much more than 2 years active.
- If we go for 5.7 :
We could release it this summer (2015) , but that would mean that 7.0
wouldn't come before summer 2016.
Releasing a 5.7 will lean the release cycle curve, but it is not mandatory,
that should be debatted.
Decisions should be taken now : aka in 2014.
Taking decisions later than this will lead to a rush in release process,
wich is very bug/error prone, and should be prevented.
Thank you.
Julien.Pauli