Define a flag --future to enable the most probable future shipping config

src/flag-definitions.h

Index: src/flag-definitions.h
diff --git a/src/flag-definitions.h b/src/flag-definitions.h
index 41e0c43e0650edb83c1e9af836ef3022193d4507..e6ff42656a84e991bad3bee3d2844b9c8358b357 100644
--- a/src/flag-definitions.h
+++ b/src/flag-definitions.h
@@ -254,6 +254,13 @@ HARMONY_STAGED(FLAG_STAGED_FEATURES)
 HARMONY_SHIPPING(FLAG_SHIPPING_FEATURES)
 #undef FLAG_SHIPPING_FEATURES
 
+DEFINE_BOOL(future, false,
+            "Implies all staged features that we want to ship in the "
+            "not-too-far future")
+DEFINE_IMPLICATION(future, ignition_staging)
+DEFINE_IMPLICATION(future, turbo)
+DEFINE_IMPLICATION(future, es_staging)

[Michael Hablich, 2016/10/14 08:29:32]

I am hesitant on this one. The performance bar for new language features is much
lower than for our pipelines. I think this flag even only is used for activating
the features on Clusterfuzz. --harmony-staging are the features which one can
enable via about:flags AFAIK.

Language features should be added one at a time to this configuration, not in
bulk.

+
 // Flags for experimental implementation features.
 DEFINE_BOOL(compiled_keyed_generic_loads, false,
             "use optimizing compiler to generate keyed generic load stubs")