<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Eol on kalfaoglu.net</title><link>https://blog.kalfaoglu.net/tags/eol/</link><description>Recent content in Eol on kalfaoglu.net</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kalfaoglu.net/tags/eol/index.xml" rel="self" type="application/rss+xml"/><item><title>PHP 8.2 Turns Off the Lights in December: Is Your Stack Ready?</title><link>https://blog.kalfaoglu.net/posts/2026-06-17-php-82-eol-countdown-en/</link><pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.kalfaoglu.net/posts/2026-06-17-php-82-eol-countdown-en/</guid><description>&lt;p&gt;On June 4, 2026, the PHP team pushed two releases: &lt;a href="https://www.php.net/archive/2026.php"&gt;PHP 8.4.22 and PHP 8.5.7&lt;/a&gt;, both routine bug-fix updates. Notice what&amp;rsquo;s missing: no 8.2 release, no 8.3 release. That&amp;rsquo;s not an oversight — it&amp;rsquo;s the lifecycle working as designed. Once a PHP branch exits active support, it receives security patches only when a qualifying CVE appears. Routine bug fixes stop. June was a bug-fix month, so 8.2 and 8.3 sat it out.&lt;/p&gt;</description></item></channel></rss>