# PHP 5.x Documentend End Of Life Dates - Thread: https://externals.io/message/61920 - Original archive: https://news-web.php.net/php.internals/61920 - Started by hakre on 2012-08-01T13:13:34+00:00 - Messages: 15 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #61920 — hakre — 2012-08-01T13:13:34+00:00 URL: https://externals.io/message/61920#61920 I have some simple questions about PHP 5.x End Of Life (EOL) dates: PHP 5.0 - Is there some official news-item or changelog entry on php.net that says at which date PHP 5.0 went End Of Life? PHP 5.2 - Does the "End Of Support" that was announced twice for PHP 5.2 has the same meaning as "End Of Life"? Is there a reason why the naming has been changed btw? PHP 4 for example was declared End Of Life but it looks like it wasn't much of a mode to use that terminology until the 2011 RFC about the release process came to life. And what about EOL of PHP 5.3, is there a date? According to the new release process it is already EOL because it's over three years now, however the RFC vote was in that lifetime so I assume that probably there is some transistion phase. If so, is there a planned date? Any thoughts/plans about PHP 5.3 EOL? Cheers -- hakre --- ## #61931 — Kris Craig — 2012-08-01T18:02:11+00:00 URL: https://externals.io/message/61920#61931 · In reply to: #61920 > I have some simple questions about PHP 5.x End Of Life (EOL) dates: > > PHP 5.0 - Is there some official news-item or changelog entry on php.netthat says at which date PHP 5.0 went End Of Life? > > PHP 5.2 - Does the "End Of Support" that was announced twice for PHP 5.2 > has the same meaning as "End Of Life"? > > Is there a reason why the naming has been changed btw? PHP 4 for example > was declared End Of Life but it looks like it wasn't much of a mode to use > that terminology until the 2011 RFC about the release process came to life. > > And what about EOL of PHP 5.3, is there a date? According to the new > release process it is already EOL because it's over three years now, > however the RFC vote was in that lifetime so I assume that probably there > is some transistion phase. If so, is there a planned date? Any > thoughts/plans about PHP 5.3 EOL? > > Cheers > > -- hakre > As far as I know (somebody please correct me if I'm wrong!), we provide legacy support to the previous tenths version increment only. In a practical sense, I think that essentially means EOL. Again, somebody please correct me if I'm mistaken, but I haven't seen any 5.2.x commits/etc since 5.4 was introduced. It's no longer on the main downloads page. Whether it's "officially" EOL or not I'm not sure, but in a practical sense I think it basically is. --Kris --- ## #61933 — Rasmus Lerdorf — 2012-08-01T18:11:41+00:00 URL: https://externals.io/message/61920#61933 · In reply to: #61920 > I have some simple questions about PHP 5.x End Of Life (EOL) dates: > > PHP 5.0 - Is there some official news-item or changelog entry on php.net that says at which date PHP 5.0 went End Of Life? > > PHP 5.2 - Does the "End Of Support" that was announced twice for PHP 5.2 has the same meaning as "End Of Life"? > > Is there a reason why the naming has been changed btw? PHP 4 for example was declared End Of Life but it looks like it wasn't much of a mode to use that terminology until the 2011 RFC about the release process came to life. > > And what about EOL of PHP 5.3, is there a date? According to the new release process it is already EOL because it's over three years now, however the RFC vote was in that lifetime so I assume that probably there is some transistion phase. If so, is there a planned date? Any thoughts/plans about PHP 5.3 EOL? No date for 5.3 yet. Depends how development goes on the next version after 5.4. EOL announcements are in the release announcements. 5.2 EOL was announced here: http://www.php.net/archive/2010.php#id2010-07-22-1 -Rasmus --- ## #61935 — keisial@gmail.com — 2012-08-01T18:16:03+00:00 URL: https://externals.io/message/61920#61935 · In reply to: #61931 > > > > […] > As far as I know (somebody please correct me if I'm wrong!), we provide > legacy support to the previous tenths version increment only. In a > practical sense, I think that essentially means EOL. Again, somebody > please correct me if I'm mistaken, but I haven't seen any 5.2.x commits/etc > since 5.4 was introduced. It's no longer on the main downloads page. > Whether it's "officially" EOL or not I'm not sure, but in a practical > sense I think it basically is. > > --Kris There should be a page like http://www.php.net/ancient-versions listing the versions with the date they went EOL and how much time has passed since them. Some scary warnings about "Known remote code execution vulnerabe" may be good too. The goal? To serve as single page where you point people when to convince them to upgrade. --- ## #61937 — Kris Craig — 2012-08-01T18:24:09+00:00 URL: https://externals.io/message/61920#61937 · In reply to: #61935 > > > […] > php.netthat says at which date PHP 5.0 went End Of Life? > > […] > use > > […] > life. > > […] > there > > […] > commits/etc > > […] > There should be a page like http://www.php.net/ancient-versions listing > the > versions with the date they went EOL and how much time has passed since > them. > Some scary warnings about "Known remote code execution vulnerabe" may be > good too. > The goal? To serve as single page where you point people when to > convince them > to upgrade. > > +9999 =) --Kris --- ## #61940 — Ferenc Kovacs — 2012-08-01T18:45:25+00:00 URL: https://externals.io/message/61920#61940 · In reply to: #61935 > > > […] > php.netthat says at which date PHP 5.0 went End Of Life? > > […] > use > > […] > life. > > […] > there > > […] > commits/etc > > […] > There should be a page like http://www.php.net/ancient-versions listing > the > versions with the date they went EOL and how much time has passed since > them. > Some scary warnings about "Known remote code execution vulnerabe" may be > good too. > The goal? To serve as single page where you point people when to > convince them > to upgrade. > > what should be the EOL date/version for the 5.2 branch? we released multiple versions after the first EOL announcement. -- Ferenc Kovács @Tyr43l - http://tyrael.hu --- ## #61944 — Larry Garfield — 2012-08-02T04:03:10+00:00 URL: https://externals.io/message/61920#61944 · In reply to: #61937 > > […] > +9999 =) > > --Kris Speaking as someone who has to deal with vendors that are still being stubborn about upgrading from PHP 5.2, and who was the lead organizer of the GoPHP5 project years ago, dear god please yes! --Larry Garfield --- ## #61945 — Kris Craig — 2012-08-02T04:30:53+00:00 URL: https://externals.io/message/61920#61945 > > > > […] > the > > […] > > Feel free to submit a patch against http://www.php.net/releases/ First we'll need to consolidate the information regarding when each version was EOL'd. Are they all in news announcements, or are they scattered between announcements, listserv threads, etc? If we're going to do this, we may as well cover as many of the /releases entries as possible; hopefully we'll be able to find the dates for most of them. Any ideas? I'd be happy to do the actual grunt work but I'm not sure where to look, particularly for older 4.x stuff. --Kris --- ## #61946 — Adam Harvey — 2012-08-02T05:00:37+00:00 URL: https://externals.io/message/61920#61946 · In reply to: #61945 > First we'll need to consolidate the information regarding when each version > was EOL'd. Are they all in news announcements, or are they scattered > between announcements, listserv threads, etc? If we're going to do this, > we may as well cover as many of the /releases entries as possible; > hopefully we'll be able to find the dates for most of them. > > Any ideas? I'd be happy to do the actual grunt work but I'm not sure where > to look, particularly for older 4.x stuff. I'm having a look at this now — we have enough information in the release array to make this work pretty much automatically, I think. Should have something up to look at tonight. Adam --- ## #61947 — Adam Harvey — 2012-08-02T06:35:36+00:00 URL: https://externals.io/message/61920#61947 · In reply to: #61946 > > > […] > > I'm having a look at this now — we have enough information in the > release array to make this work pretty much automatically, I think. > > Should have something up to look at tonight. Or even this afternoon. :) I've added http://php.net/eol (coming soon to a mirror near you; it's not up yet): at present, it's pretty bare bones, just listing the date of the last release on each unsupported branch, and with an optional notes field. It's not linked from anywhere yet — I have a patch that will add it to the sidebar on /releases, as Rasmus suggested, but let's get the EOL page itself worked out first. Thoughts? (Do we even want to auto-fill this from $OLDRELEASES, or would we rather have a manual array?) Specific notes on vulnerabilities to add to branches? Better versions of the copy in the initial blurb? Adam --- ## #61949 — Peter Cowburn — 2012-08-02T07:56:38+00:00 URL: https://externals.io/message/61920#61949 · In reply to: #61947 > Thoughts? (Do we even want to auto-fill this from $OLDRELEASES, or > would we rather have a manual array?) Specific notes on > vulnerabilities to add to branches? Better versions of the copy in the > initial blurb? Why is this information not just displayed on "Unsupported Historical Releases" (/releases)? Do you have plans for the EOL page that wouldn't be suitable for the other one? My worry is spreading this information across multiple places, when we already have a very detailed page about unsupported versions. The X.Y version table could be listed at the top of /releases to give a quick summary, before the detail for each individual version listed chronologically. We could add more notes like the existing "Support for PHP 4 has been discontinued since 2007-12-31." at the appropriate places in that list. --- ## #61950 — Adam Harvey — 2012-08-02T08:02:19+00:00 URL: https://externals.io/message/61920#61950 · In reply to: #61949 > > > […] > > Why is this information not just displayed on "Unsupported Historical > Releases" (/releases)? Do you have plans for the EOL page that > wouldn't be suitable for the other one? My worry is spreading this > information across multiple places, when we already have a very > detailed page about unsupported versions. The X.Y version table could > be listed at the top of /releases to give a quick summary, before the > detail for each individual version listed chronologically. We could > add more notes like the existing "Support for PHP 4 has been > discontinued since 2007-12-31." at the appropriate places in that > list. That could definitely work as well. I've done it as a separate page because that was the suggestion from Kris and Larry (and because I wasn't really sure how it would come together to start with), but there's no particular reason it couldn't be integrated into /releases. It probably is short enough. Adam --- ## #61952 — Lester Caine — 2012-08-02T08:40:20+00:00 URL: https://externals.io/message/61920#61952 · In reply to: #61947 Adam Harvey wrote: > Thoughts? (Do we even want to auto-fill this from $OLDRELEASES, or > would we rather have a manual array?) Specific notes on > vulnerabilities to add to branches? Better versions of the copy in the > initial blurb? A little academic now, but I was convinced that 5.1 had some more official releases? 5.1.6 had a number of bugs that prevent Firebird/Interbase working and we had 2.1.7 running which fixed the problem. Was that never released officially? Academic as I say, and everything was moved to 5.2 quite quickly as it rolled out without any problems and removed some of the problems created by 5.1 itself - such as the date code clashes ;) Can I make a request for an additional column which links to the relevant migration guide. That would at least be a start, but I'm currently trying to work through 5.3 and 5.4 migration guides to see if they DO have fixes for the 'problems' that are coming up on porting code from PHP5.2 ... The statement "Most improvements in PHP 5.3.x have no impact on existing code." should perhaps be augmented with a least some reference to ensuring that the .ini settings are compatible with PHP5.2 code? Is there a document that shows what settings .ini should have to maintain compatibility? I could not find anything suitable although everything is documented somewhere. I think one thing that is preventing many ISP's switching is the removal of register_globals ? Heck *I* still have code which will not work without register_globals and the time it would take to rework that code is just another job I don't have time for :( The fact that 5.3 still supports this is given as the reason for not switching to 5.4 just yet. Not a problem for this list perhaps, but many of the end users probably have no idea how to fix this particular problem as they are using third part code that relies on it? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk --- ## #61956 — hakre — 2012-08-02T09:42:41+00:00 URL: https://externals.io/message/61920#61956 · In reply to: #61947 > I've added http://php.net/eol Thank you. For PHP 5.x I had created a blog post which is not that complete just reflects the work on scanning through the news items: http://hakre.wordpress.com/2012/07/30/historic-php-end-of-life-dates/ I started this to create a timeline graphic, a first draft is: http://i.stack.imgur.com/HYKZm.png which in turn made me asking questions here for the parts that were not clear to me. -- hakre --- ## #61957 — hakre — 2012-08-02T09:47:09+00:00 URL: https://externals.io/message/61920#61957 · In reply to: #61933 > No date for 5.3 yet. Depends how development goes on the next version > after 5.4. EOL announcements are in the release announcements. 5.2 EOL > was announced here: http://www.php.net/archive/2010.php#id2010-07-22-1 Yes, I've seen that with release announcements often (but not always) a (more or less concrete) statement was given for support, but the naming is far from being consistent. For example, PHP 5.2 has multiple onces', three in total. Actually the questions I asked initially were born because of reading those announcements. So if I may summarize based on my own observations and your feedback:  * PHP 5.0 has no EOL date (because there was never a release            announcement with an EOL),  * PHP 5.1 has one EOL date (2006-11-02 "Obsoletion"),  * PHP 5.2 has three EOL dates (2010-07-22 "End Of Active Support";            2010-12-09 and 2010-12-16 "End Of Support"),  * PHP 5.3 has none yet (TBA) and  * PHP 5.4 also has none yet even though the accepted release            procedure[1] suggests it has to have one already            (2015-03-01 "EOL"). Does this summary for EOL dates of 5.x versions reflect the current status quo appropriately? And what are the plans to practically introduce the accepted release procedure? I ask because it is documented and announced to be voted into order but the feedback you have given so far suggests it is not for the End Of Life dates. So I think this can benefit from some clarification, too. Thank you for your ongoing support -- hakre