Componentize VersionInfo.

chrome/browser/ui/views/app_list/win/app_list_service_win.cc

Index: chrome/browser/ui/views/app_list/win/app_list_service_win.cc
diff --git a/chrome/browser/ui/views/app_list/win/app_list_service_win.cc b/chrome/browser/ui/views/app_list/win/app_list_service_win.cc
index a079122239916360f72bbc308d3ac66ffa29e9fd..9a4e98d975e160e7d9ee6d0cda26532f734df40c 100644
--- a/chrome/browser/ui/views/app_list/win/app_list_service_win.cc
+++ b/chrome/browser/ui/views/app_list/win/app_list_service_win.cc
@@ -330,14 +330,14 @@ void AppListServiceWin::ScheduleWarmup() {
   // to the server-side analysis tool, reducing this period to 10 sec in Dev
   // builds and Canary, where profiler instrumentations are enabled.
   switch (chrome::VersionInfo::GetChannel()) {
-    case chrome::VersionInfo::CHANNEL_UNKNOWN:
-    case chrome::VersionInfo::CHANNEL_CANARY:
+    case version_info::Channel::UNKNOWN:
+    case version_info::Channel::CANARY:
       kInitWindowDelay = 10;
       break;
 
-    case chrome::VersionInfo::CHANNEL_DEV:
-    case chrome::VersionInfo::CHANNEL_BETA:
-    case chrome::VersionInfo::CHANNEL_STABLE:
+    case version_info::Channel::DEV:
+    case version_info::Channel::BETA:
+    case version_info::Channel::STABLE:
       // Except on Canary, don't bother scheduling an app launcher warmup when
       // it's not already enabled. Always schedule on Canary while collecting
       // profiler data (see comment above).