On Fri, Mar 21, 2025 at 10:13:51PM +0100, Sylvain Beucler wrote: > > - For bullseye-lts and *-elts we should be able to keep support, as we > should be able to write fixes for this PHP code base. However since upstream > activity for 5.2.x is very low, we could also drop support in bullseye-lts, > though I'm neutral on this point. > I will limit myself specifically to the matter of php-horde-* in LTS. I am neutral-ish as well, but it seems prudent to consider that there may be a benefit in declaring the EOL concurrent with EOL in bookworm.
If it seems *likely* that writing patches/backporting for bullseye will be feasible without too much work, then we can continue the support. However, if it seems likely that any non-trivial CVE and patch backport will get stuck, then it seems better to not wait for EOL. This way, users can plan for migration without the pressure of an open (critical) CVE that can't/won't get fixed. Have you (or can you) assess whether we are more likely to land on one side or the other? Regards, -Roberto -- Roberto C. Sánchez
