> > The flag name `cdc_enabled` is simple and, without adjectives, does not > imply "experimental" or "beta" or anything like that. > It does make life easier for both operators and the C* developers.
I would be all for a mv_enabled option, assuming it's enabled by default for all existing branches. I don't think saying that you are meant to read NEWS.txt before upgrading a patch is acceptable. Most people don't, and expecting them to is a bit insane. Also Assuming that if they read it they'd understand all implications is also a bit questionable. If deemed suitable to turn it off that can be done in the next major/minor, but I think that would be unlikely, as we should really require sufficient evidence that it's dangerous which I just don't think we have. I'm still of the opinion that MV in their current state are no worse off than a lot of other features, and marking them as experimental and disabling now would just be detrimental to their development and annoy users. Also if we give them that treatment then there a whole load of other defaults we should change and disable which is just not acceptable in a patch release. It's not really necessary anyway, we don't have anyone crying bloody murder on the mailing list about how everything went to hell because they used feature x. No one has really provided any counter evidence yet that MV's are in some awful state and they are going to shoot users. There are a few existing issues that I've brought up already, but they are really quite minor, nothing comparable to "lol you can't repair if you use vnodes, sorry". I think we really need some real examples/evidence before making calls like "lets disable this feature in a patch release and mark it experimental" > I personally believe it is better to offer the feature as experimental > until we iron out all of the problems What problems are you referring to, and how exactly will we know when all of them have been sufficiently ironed? If we mark it as experimental how exactly are we going to get people to use said feature to find issues?
