Refactoring startup logic for upcoming FRE changes (non-Win 10).

chrome/browser/first_run/first_run_features.h

Index: chrome/browser/first_run/first_run_features.h
diff --git a/chrome/browser/first_run/first_run_features.h b/chrome/browser/first_run/first_run_features.h
new file mode 100644
index 0000000000000000000000000000000000000000..8da3b592e0661ba689f97f56c1150d267ab2f70a
--- /dev/null
+++ b/chrome/browser/first_run/first_run_features.h
@@ -0,0 +1,16 @@
+// Copyright (c) 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.
+
+#ifndef CHROME_BROWSER_FIRST_RUN_FIRST_RUN_FEATURES_H_
+#define CHROME_BROWSER_FIRST_RUN_FIRST_RUN_FEATURES_H_
+
+#include "base/feature_list.h"
+
+namespace features {
+
+extern const base::Feature kUseConsolidatedFirstRun;

[grt (UTC plus 2), 2016/07/29 06:56:15]

is chrome/common/chrome_features.h an appropriate place for this?

[tmartino, 2016/07/29 15:28:12]

The PMs on this have indicated a desire to do a fair amount of future
fiddling/tweaking/general experimentation (for instance, the Win10 portion of
this refresh will be tested in a few different layouts) so I thought it made
sense to group these new features together as they appear, to avoid including
them all over the place, and to reduce the overhead of going to top-level
/chrome/ OWNERS for such changes.

Weak preference though.

[grt (UTC plus 2), 2016/08/01 06:23:14]

Acknowledged.

+
+}  // namespace features
+
+#endif  // CHROME_BROWSER_FIRST_RUN_FIRST_RUN_FEATURES_H_