New issue
Advanced search Search tips

Issue 923584 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Create top level directory for the cross-platform updater project

Project Member Reported by sorin@chromium.org, Jan 18 (4 days ago)

Issue description

Until crbug.com/923128 is approved, use this subcategory for updater bugs.



 

Comment 1 by sorin@chromium.org, Jan 18 (4 days ago)

# Objective
The objective is to create a fourth generation of client updaters for Google
desktop client software, including Chrome. These updaters will be built
from a common, platform neutral code base, as part of the Chrome build.

In this context, the desktop platforms include Mac and Windows.

The cross platform updater is reusing src/components/update_client and its
dependencies.

There are many reasons to start a new code base for updaters:
* There is a great deal of common features and behavior that can be implemented
once, and then reused on many platforms, reducing the amount of client code
duplication.
* To efficiently and reliably update a large user base, non-trivial algorithms
for checking for updates, applying updates, gathering metrics, and load
shedding are being used. Implementing such algorithms in a consistent manner
is desirable.
* The code for the current updaters is +10 years old. While this is not a bad
thing, the code does not benefit from the improvements in developer tool
chains such as the Chromium dev tools, especially the build, security,
and stability aspects.

Sign in to add a comment