Sure, I'm even arguing that 2.4.8 could possibly be the final release. No objection of course to continuing to backport to 2.4.x where appropriate and cutting 2.4.9 later in the year as a final EOL release, either.
On Wed, Mar 3, 2021 at 12:59 PM Dongjoon Hyun <dongjoon.h...@gmail.com> wrote: > Thank you, Sean. > > Ya, exactly, we can release 2.4.8 as a normal release first and use 2.4.9 > as the EOL release. > > Since 2.4.7 was released almost 6 months ago, 2.4.8 is a little late in > terms of the cadence. > > Bests, > Dongjoon. > > > On Wed, Mar 3, 2021 at 10:55 AM Sean Owen <sro...@gmail.com> wrote: > >> For reference, 2.3.x was maintained from February 2018 (2.3.0) to Sep >> 2019 (2.3.4), or about 19 months. The 2.4 branch should probably be >> maintained longer than that, as the final 2.x branch. 2.4.0 was released in >> Nov 2018. A final release in, say, April 2021 would be about 30 months. >> That feels about right timing-wise. >> >> We should in any event release 2.4.8, yes. We can of course choose to >> release a 2.4.9 if some critical issue is found, later. >> >> But yeah based on the velocity of back-ports to 2.4.x, it seems about >> time to call it EOL. >> >> Sean >> >
