Hi Tim, On Tue, Jan 04, 2022 at 06:41:14PM +0100, Tim Düsterhus wrote: > On 12/19/21 7:36 PM, Nemo wrote: > > Is there any way for users to find out exact EoL dates in advance, or is > > there an accepted answer for what Q1/Q2/Q3/Q4 would usually mean here? > > I believe you missed Nemo's email and you're probably in the best (and > only?) position to answer it.
Yep, thanks for pointing that one, I indeed let it rot and forgot about it. > Semi-related: 1.7 should probably receive its final release and then be > marked as EOL, as Q4 2021 definitely is in the past now :-) Indeed. I had a look at the relevant patches since the last version, and am only seeing minor ones. As such I'd rather not emit any new version delivering a bad signal, than risking to break something that possibly works well enough for users. Question to any possible user of 1.7: is anyone currently on 1.7.14 (the latest one) facing a problem upgrading to a more recent branch, and waiting for a particular fix to be backported into 1.7 for the time it takes to solve the upgrade issue ? Or is anyone waiting for a specific fix there for a deployment that's about to reach EOL in a few weeks at best ? Without positive responses by the end of the week, I guess we could then declare it EOL and change its color in the table. 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 ? Cheers, Willy
