Updates:
Status: Assigned
Owner: [email protected]
Comment #5 on issue 22158 by [email protected]: Daily Auto-Updating Chromium
Build w/ Crash Data Reporting
http://code.google.com/p/chromium/issues/detail?id=22158
Short term:
1. Official build-bot that runs nightly using the CL for the latest
green Chromium build.
2. Builds are stored in a convenient location where QA can use them for
validation.
3. Builds are not signed.
4. Builds can be installed along-side Stable, Beta, or Dev channel
releases without side-effects.
5. Builds have unique branding that distinguishes them as
dangerous/untested/scary.
6. Public release via web server or not at all. May be internal only.
7. Manual updates.
Medium Term:
1. Unique product ID. (so we don't pollute the config for the updater)
2. Updates via normal updater.
3. Updates hosted on production systems for download.
4. Everything automated except approval of the config for the updater.
(no updates on holidays/weekends?)
5. Binaries available to the public.
Long Term:
1. Builds are signed.
2. Build official releases without scary branding in parallel for quick
and easy released when blessed by
QA.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
