On Wed, Jan 05, 2022 at 05:07:16PM +0100, Tim Düsterhus wrote:
> > This makes me think that this should also mark the turn for 2.0 to
> > enter the "critical fixes only" status. We all know it doesn't mean
> > much, beyond giving us an excuse for producing releases less often,
> > but this is also what such users of a 3-years old version are usually
> > counting on. Any objection ?
> 
> I'd suggest to mark 2.0 as "critical fixes only" in May - 2 years before the
> EOL in Q2 2024. We did the same for 1.8 which was marked as critical fixes
> only at the end of 2020 (i.e. 2 years before Q4 2022).

Yeah that's a good point, that works for me (even less changes to write) :-)

Cheers,
Willy

Reply via email to