A second vote for any bugfixes we can get for 2.1, we'd probably use it. We are finally getting traction behind upgrades with an automated upgrade/rollback for 2.1 --> 2.2, but it's going to be a while.
Aaron, if you want to use our 2.1-2.2 migration tool, we can talk about at the next MPLS meetup. I'm not saying its the hot sauce, but it does seem to do things fairly well from the 10 or so clusters we've done with it (and the bugfixes it has shown). The code hasn't been OSS'd yet, but it is slated to be. On Tue, Jan 8, 2019 at 8:49 AM Aaron Ploetz <aaronplo...@gmail.com> wrote: > 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 > >
