Re: [RFC] Sunset PECL

From: Date: Wed, 11 Nov 2026 20:00:32 +0000
Subject: Re: [RFC] Sunset PECL
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-133080@lists.php.net to get a copy of this message
On Tue, 10 Nov 2026, at 16:42, Derick Rethans wrote: > > Maintainers can remove existing releases (it's hidden somewhere), and > admins, like me, can remove any existing release. Ah I figured that might be the case! > > - a mitigation contingency to this risk: if a serious vulnerability is > > identified in a listed static package, we remove the affected > > package version(s) manually. > > That would require hacking some XML and removing files, but it can be > done. But as the period is only 6 months, then that is not a large > problem. Yeah that's what I was hoping; even if it's just a bit of manual work to remove them, 6 months is hopefully not too long a period to manage any potential risks that surface. > > - reduce the overall timeline to 1yr, bring forward all the 2029 > > dates to 2027. That's 6 months of "heads up", and 6 months of "read > > > > only mode plus brownouts" before shutdown ad the end of 2027. Ah sorry - misread, but I do think reducing to 6 months of read-only phase will minimise the surface risk that Rowan pointed out, and also minimise any potential manual work we might to carry out to manage vulnerabilities. I've updated the RFC wording accordingly to mention the approach to mitigate any potential vulnerability risks, and reduce the timeline to one year overall. Thanks folks, James

« previous php.internals (#133080) next »