Hi internals.
As you may know/remember , PHP 5.5 has been released two years ago.
We've released 26 versions so far (24 would be the "normal" computing, but
we always got some bad releases, mainly from human failure factor).
The actual stable 5.5 is PHP 5.5.26.
This week, I'm going to tag the last 5.5 RC : 5.5.27RC.
Then will follow the last "normal process" 5.5 release : 5.5.27.
The PHP 5.5 branch is going to enter in security only, and in the same
time, PHP 5.4 will finally die
As a contributor, you are still allowed to commit to the 5.5 branch until
the next RC, that is until tomorrow tuesday or wednesday 24th of June.
After this date, I ask every contributor to consider 5.5 as beeing in sec
only, and to commit their code to the 5.6 branch (and merge up) thus to
not commit anything to the 5.5 branch anymore. 5.6 will become the lowest
branch to commit in.
For security related commits, please talk to the RM (mainly myself) to know
what to do. Also remember about our security@ mailing list.
To prevent leaks, we are going to restrict the commit access to the 5.5
branch in few days, so that if you forget about it, you'll be denied by git
if trying to push to 5.5 => push to 5.6 instead ;-)
Only RM will keep their commit access to the 5.5 branch.
Our usual security process does not change however, after 5.5.27 is
released, 5.5 will have no more release until enough security bugs are
found. That may still happen every month, or not.
Thank you for your understanding, and happy PHP Hacking.
Julien Pauli
Hi!
The PHP 5.5 branch is going to enter in security only, and in the same
time, PHP 5.4 will finally die
I think http://php.net/supported-versions.php says we end 5.4 support on
14 Sep 2015 so we have 2 more releases? Unless we have reason to change
it or that page is wrong?
In general, it would be nice to have a pre-announced final release
instead of announcing it post-factum.
Stas Malyshev
smalyshev@gmail.com
Hi!
The PHP 5.5 branch is going to enter in security only, and in the same
time, PHP 5.4 will finally die
I think http://php.net/supported-versions.php says we end 5.4 support on
14 Sep 2015 so we have 2 more releases? Unless we have reason to change
it or that page is wrong?
By default, the EOL dates are automatically calculated based on when
the first release on a branch occurred, but these can be overridden as
needed — see https://github.com/php/web-php/blob/master/include/branches.inc#L5-L21
for the gory details. I believe I set the 5.4 dates based on e-mails
last year, but don't have the references to hand.
If we have specific dates in mind for 5.4 and 5.5, I'm happy to update
the Web site to match (and do whatever Twitter publicity is required
via @official_php).
In general, it would be nice to have a pre-announced final release
instead of announcing it post-factum.
Agreed.
Adam
Hi,
-----Original Message-----
From: Stanislav Malyshev [mailto:smalyshev@gmail.com]
Sent: Monday, June 22, 2015 11:10 PM
To: Julien Pauli; PHP Internals; Ferenc Kovacs; Stanislav Malyshev; Kalle Sommer
Nielsen; Pierre Joye; David Soria Parra; Anatol Belsky
Subject: [PHP-DEV] Re: Announcing PHP 5.5 security-onlyHi!
The PHP 5.5 branch is going to enter in security only, and in the same
time, PHP 5.4 will finally die
I think http://php.net/supported-versions.php says we end 5.4 support on
14 Sep 2015 so we have 2 more releases? Unless we have reason to change it or
that page is wrong?In general, it would be nice to have a pre-announced final release instead of
announcing it post-factum.
Actually I was relying on that page as well. While it would be great if 5.4 branch were blocked, as we would branch 7.0 ... disregarding were it wrong or not, IMHO 14th September should be the date. Even if the page is wrong, the info is public, people might rely on it. It doesn't enforce 5.4 to release without the reason, but it gives room to announce the EOL properly.
Regards
Anatol
Hi,
Actually I was relying on that page as well. While it would be great if 5.4 branch were blocked, as we would branch 7.0 ... disregarding were it wrong or not, IMHO 14th September should be the date. Even if the page is wrong, the info is public, people might rely on it. It doesn't enforce 5.4 to release without the reason, but it gives room to announce the EOL properly.Regards
Anatol
+1 If a page says "Security Support Until 14 Sep 2015", it may receive
support for longer, but it's really wrong to short it (at least without
exceptional reasons).
And, if that's not how it really works, the page wording should be
changed ASAP, and before 5.4 EOL (when people will hurry to see next one
time frame).
@Adam, I was expecting the "gory details" to involve a of PHP commiters
with black robes, faces hidden behind their hoods meeting overnight and
an absurdly complex algorithm involving lunar cycles. instead you point
to a manual override, but no descripcion on how it gets changed.
@Adam, I was expecting the "gory details" to involve a of PHP commiters with
black robes, faces hidden behind their hoods meeting overnight and an
absurdly complex algorithm involving lunar cycles. instead you point to a
manual override, but no descripcion on how it gets changed.
I left the robes out for time. The lunar cycle part is technically
correct (the best kind of correct).
That file's in the web/php repository, so anyone with web karma can
change it. I've added a 5.5 block to say that the last "normal"
release will be around the 10th of July. (I know it'll probably
actually be the 9th in much of the world, but let's cover Australia,
China, Japan, NZ, and friends.)
Stas, what are your plans for 5.4? Do you want me to adjust the EOL
date for that too?
Adam
On Mon, Jun 22, 2015 at 11:10 PM, Stanislav Malyshev smalyshev@gmail.com
wrote:
Hi!
The PHP 5.5 branch is going to enter in security only, and in the same
time, PHP 5.4 will finally die
I think http://php.net/supported-versions.php says we end 5.4 support on
14 Sep 2015 so we have 2 more releases? Unless we have reason to change
it or that page is wrong?In general, it would be nice to have a pre-announced final release
instead of announcing it post-factum.
hi,
I think it is a good idea to keep the current system: we have an estimation
based on the release date, but co-ordinate the actual release/extended
support/eol dates.
I agree that it make sense to explicitly state in the last release's
announcement that the support for that particular version has ended, plus
if by any chance the last 5.4 release would happen together with the next
5.5 release then that would make it more consistent too, but ofc. that
depends on what do we have in the pipe.
Hi internals.
As you may know/remember , PHP 5.5 has been released two years ago.
We've released 26 versions so far (24 would be the "normal" computing, but
we always got some bad releases, mainly from human failure factor).The actual stable 5.5 is PHP 5.5.26.
This week, I'm going to tag the last 5.5 RC : 5.5.27RC.
Then will follow the last "normal process" 5.5 release : 5.5.27.
The PHP 5.5 branch is going to enter in security only, and in the same
time, PHP 5.4 will finally die
You should mail such a headsup to announce@ couple of months before
the "final release date".
So if September 14th is the final release date, I'd say sending a
"REMINDER: 5.4 GOES SECURITY ONLY SEPT 14th" mail to announce@ July
14th (or August 14th?) would be nice.
-Hannes
Hi!
You should mail such a headsup to announce@ couple of months before
the "final release date".
So if September 14th is the final release date, I'd say sending a
"REMINDER: 5.4 GOES SECURITY ONLY SEPT 14th" mail to announce@ July
14th (or August 14th?) would be nice.
Sep 14th does not coincide with planned release date (which if on
schedule is supposed to be on September 3) and isn't even a Thursday,
but we can make September 3 release final or the next one. I'll add a
note in the next releases of 5.4 about upcoming end of support, and we
probably should add a note in 5.5 release announcements too.
--
Stas Malyshev
smalyshev@gmail.com
On Wed, Jun 24, 2015 at 8:01 PM, Stanislav Malyshev smalyshev@gmail.com
wrote:
Hi!
You should mail such a headsup to announce@ couple of months before
the "final release date".
So if September 14th is the final release date, I'd say sending a
"REMINDER: 5.4 GOES SECURITY ONLY SEPT 14th" mail to announce@ July
14th (or August 14th?) would be nice.Sep 14th does not coincide with planned release date (which if on
schedule is supposed to be on September 3) and isn't even a Thursday,
but we can make September 3 release final or the next one. I'll add a
note in the next releases of 5.4 about upcoming end of support, and we
probably should add a note in 5.5 release announcements too.
Makes sense, that will be done.
Julien Pauli