Normally we prefer new features to go to trunk. In some rare cases, when the risk is low and the value of a new feature is high, we make exceptions - but usually early in a major version life cycle, and mostly in the past, when we were a lot more lax about such things.
In this particular case I think 4.0(+) is the right major version for this change to land on. > On 12 Nov 2019, at 22:25, Ekaterina Dimitrova > <ekaterina.dimitr...@datastax.com> wrote: > > Hello, > According to the official Cassandra web page no new features could be > submitted for version 3.11. I am not sure whether this also covers some > small improvements? > Short example - CASSANDRA-12197 > > Thank you in advance > > Best regards, > Ekaterina Dimitrova | Software Engineer > ekaterina.dimitr...@datastax.com | datastax.com > <http://datastax.com/?utm_campaign=FY20Q2_CONSTELLATION&utm_+medium=email&utm_source=signature> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
