Thanks for the heads-up. I will update the post. Regards,
Carlos Juzarte Rolo Cassandra Consultant / Datastax Certified Architect / Cassandra MVP Pythian - Love your data rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin: *linkedin.com/in/carlosjuzarterolo <http://linkedin.com/in/carlosjuzarterolo>* Mobile: +351 918 918 100 www.pythian.com On Thu, Apr 12, 2018 at 5:02 AM, Michael Shuler <mich...@pbandjelly.org> wrote: > On 04/11/2018 06:12 PM, Carlos Rolo wrote: > > > > I blogged about this decision recently > > here: https://blog.pythian.com/what-cassandra-version-should-i-use-2018/ > > s/it the fact/is the fact/ typo, and possibly not 100% correct on the > statement in that sentence. > > There are commits since the last 2.1 & 2.2 releases. Generally, we'll do > a last release with any fixes on the branch, before shuttering > development on older branches. 1.0 and 1.1 had a few commits after the > last releases, but 1.2 and 2.0 both had final releases with any bug > fixes we had in-tree. I expect we'll do the same with 2.1 and 2.2 to > wrap things up nicely. > > -- > Warm regards, > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org > For additional commands, e-mail: user-h...@cassandra.apache.org > > -- --
