Speaking as a user with a few large clusters still running on 2.1, I think a final release of it with some additional fixes would be welcomed. That being said, I thought we were holding off on EOLing 2.1 until 4.0 is released. Although, the timings probably don’t need to coincide.
In short, a (non-binding) final release of 2.1 is a good idea. Thanks, Aaron > On Jan 7, 2019, at 8:01 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > > It came to my attention on IRC a week or so ago, and following up on the > ticket that someone asked if they should commit to 2.1, that developers > have been actively ignoring the 2.1 branch. If we're not committing > critical fixes there, even when we know they exist, I think it's time to > just call it EOL an do one last release of the few fixes that did get > committed. Comments? > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > For additional commands, e-mail: dev-h...@cassandra.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
