Re: [RFC] php-community: a faster-moving, community-driven PHP.
| From: | Jakub Zelenka | Date: | Sun, 15 Mar 2026 15:36:35 +0000 |
| Subject: | Re: [RFC] php-community: a faster-moving, community-driven PHP. | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-130349@lists.php.net to get a copy of this message | ||
On Sun, Mar 15, 2026 at 3:51 PM Daniil Gentili <daniil.gentili@gmail.com>
wrote:
>
>
> I don't understand the security part. Do you mean that people could report
>> security issues for those community branches? If so, then it's completely
>> unrealistic as we are already struggling with handling security issues for
>> the current branches.
>>
>
>
> I honestly do not consider seriously any argument based on "it's too much
> load for maintainers", including around security (which is still a
> responsibility of feature owners).
>
>
Except feature owners won't be able do any triaging, security impact
analysis (deciding whether it's a security issue - this is done by the
security team), allocating CVE's, test the patches in our security repo, do
the security release and publishing / updating all advisories. And I'm not
even considering extra reporting will be required by CRA. So I think you
might be underestimating the amount of work for handling security issues.
Kind regards,
Jakub