SoftwareUpdates
This will be a specification for how software updates should be presented in an existing Ubuntu installation.
Rationale
The software updates interface should maximize the voluntary and continued installation of updates across the millions of computers on which Ubuntu is installed.
Design requirements
That Ubuntu updates are split into individual packages is an irrelevant detail that must not be exposed by default. For example, Microsoft ExpertZone’s “Comparing Windows 7 to Linux” retail course claims: “Linux can require a lot of time to maintain. For example, Ubuntu (a variety of Linux) may have hundreds of updates per month.” [screenshot from Overclock.net]
- Checking for updates should not be confused with downloading updates. For example, one netbook purchaser wondered why Update Manager said it was downloading the same 91 updates every time, because she thought the updates were actually being downloaded. [Dave Morley]
Ideas
- How can we reduce/eliminate the lag between an update being published and its description being available?
- Check for security updates every day. But check for non-security updates only (a) a week after the last check or (b) when security updates are available, whichever is earlier. [mac_v]
- Is it possible to install the initial batch of updates during the installation process?
The foundations-karmic-install-updates-when-installing specification covers downloading the updates while installing Ubuntu. - evand
- The “You need to restart the computer” alert could be merged into the main window.
- How do distinguish security updates from other updates?
- Warn about trying to install updates while running on battery?
- We should collect statistics on how many people install updates how quickly. [Oli Warner]
Unresolved issues
Whether an update will require restarting, logging out, or restarting an application, should be presented before you choose to install it. How will we know this?