MidiManagerWinrt as base::FeatureList feature

media/midi/midi_features.cc

Index: media/midi/midi_features.cc
diff --git a/media/midi/midi_features.cc b/media/midi/midi_features.cc
new file mode 100644
index 0000000000000000000000000000000000000000..fa5c845665312c2730eeadcd951782311ce9c7e2
--- /dev/null
+++ b/media/midi/midi_features.cc
@@ -0,0 +1,14 @@
+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "media/midi/midi_features.h"
+
+namespace features {
+
+#if defined(OS_WIN)
+const base::Feature kUseWinrtMidiApi{"UseWinrtMidiApi",
+                                     base::FEATURE_ENABLED_BY_DEFAULT};

[Takashi Toyoshima, 2016/09/20 09:12:04]

The Feature API is used for a field trial in general, and there is a clear
guideline, go/finch101.
Generally speaking, flipping this to ENABLED_BY_DEFAULT is the last step of the
feature launch process, and need to start from DISABLED_BY_DEFAULT, and enable
it via server side configurations so that we can shutdown the feature safely.

I don't think this change need a launch review, but it's better to follow the
guideline just in case so to avoid unnecessary troubles.

[Shao-Chuan Lee, 2016/09/20 09:57:27]

Done.

+#endif
+
+}  // namespace features