There are a couple compromise options here: a) Introduce the flag (enalbe_experimental_features, or maybe one per experimental feature), set it to ‘false’ in the yaml, but have the default be ‘true’. So that if you are upgrading from a previous minor to the next without updating the yaml, you notice nothing.
b) Introduce the flag in the minor, and set it to ‘true’ in the yaml in 3.0 and 3.11, but to ‘false’ in 4.0. So the operators and in general people who know better can still disable it with one flip, but nobody would be affected by it in a minor otherwise. B might be more correct, and I’m okay with it, although I do feel that we are behaving irresponsibly as developers by allowing MV creation by default in their current state and that it’s better to correct a mistake late than later. — AY On 3 October 2017 at 10:27:58, Sylvain Lebresne (sylv...@datastax.com) wrote: Just one more data point, but I personally don't feel that disabling new MV creation (or new SAS index creation for that matter) by default _in a patch release_ is terribly nice.
