New A/B Experimentation Setting about vscode-cpptools

[sean-mcmanus]

I'm not understanding why we need a new setting and can't just change the existing setting's setting from "disabled" to "default" (a new 3rd value), i.e. I think we should do that instead. The meaning of the existing experimentalFeatures settings seems valid still and not really in conflict with the A/B experiment.

[AlexandraKemperMS]

When I talked to Bob about this he had mentioned that we still want to keep the original setting since we might have "beta" features that we want to release as an experimental feature. These are separate from A/B experiments. You can see other extensions do this as well:

[sean-mcmanus]

@AlexandraKemperMS @bobbrow I'm still not understanding. We can still have beta non-A/B experimental features with the one setting still.

• Disable: No experimental
• Enable: All experimental
• Default: beta experimental features are disabled, A/B experimental features are subject to the "rollout" randomness
  I don't see a good reason for a user to want to have different behaviors between the two either.

[github-actions]

This feature request is being closed due to insufficient upvotes. Please leave a 👍-upvote or 👎-downvote reaction on the issue to help us prioritize it. When enough upvotes are received, this issue will be eligible for our backlog.