> Should we also do a 2.1.18 release as a final cut and end commits to the
> cassandra-2.1 branch? I'm sorry I hadn't thought about this sooner.

Meh? There is nothing major in there. That said, if we want to just
say "that's it for 2.1", I guess we could do another.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Reply via email to