Description:
The Chrome bundle file obtained from the Enterprise web page lacks any version info. We should add a VERSION file as is done with the adm/admx template files.

Use case:
On the Chrome Enterprise web site, users can download adm/admx template packages (zipfiles) for stable, beta, and dev versions of Chrome. Each of those zipfiles contains a VERSION file, which shows which version of Chrome it applies to.

The full version of Chrome, GoogleChromeEnterpriseBundle64.zip (and the matching 32-bit version) lack any type of interior version information. The only way to find which specific version of Chrome it contains is installing it.

That presents a configuration management problems for administrators, who may have several versions of GoogleChromeEnterpriseBundle64.zip, and no way of telling which one is the one they need, without installing. If we can add a VERSION file to the full program zipfile, as we already to for the adm/admx zipfiles, administrators can easily tell the versions apart.


Motivation:
This is related to the description above. It's trivial to foresee an organization having many versions of the Chrome zipfile, spread among various directories. When it comes time for them to upgrade, which one should they use? As of now all they can do it install the package on a VM to find out. That is very time consuming and frustrating if they want to locate one specific version of Chrome.

Adding a VERSION file makes the process trivial, and makes the files identifiable programmatically. Plus, we already add the VERSION file to the adm/admx templates, so it is available on our end.

Existing workarounds:
Install the Chrome package to find out which version of Chrome it contains.