SoftwareUpdates

Differences between revisions 1 and 7 (spanning 6 versions)
Revision 1 as of 2009-08-26 09:39:47
Size: 315
Editor: eth0
Comment: + links to related pages
Revision 7 as of 2009-10-13 10:34:54
Size: 1945
Editor: eth0
Comment: need to update Software Sources to reflect new update settings
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
## page was renamed from SoftwareUpdatePresentation
Line 2: Line 3:

== Rationale ==

That Ubuntu updates are split into individual packages is an irrelevant detail that must not be exposed by default. For example, [[http://expertzone.microsoft.com/|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.” [``[[attachment:microsoft-linux-updates-full.jpg|screenshot]] from [[http://overclock.net/windows/569458-microsoft-attack-linux-retail-level-probably.html|Overclock.net]]]

== 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 UbuntuSpec:foundations-karmic-install-updates-when-installing specification covers downloading the updates while installing Ubuntu. - evand
 * [[Ayatana/UpdateIssues]]
 * [[FoundationsTeam/Specs/KarmicUpdatesOnShutdown]]
 * 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]
Line 5: Line 23:
 * Is it possible to install the initial batch of updates during the installation process?
 * [[Ayatana/UpdateIssues]]
 * [[FoundationsTeam/Specs/KarmicUpdatesOnShutdown]]
 * https://wiki.ubuntu.com/NotifyOSD#software-sources
 * 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?

This will be a specification for how software updates should be presented in an existing Ubuntu installation.

Rationale

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]

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?
  • Ayatana/UpdateIssues

  • FoundationsTeam/Specs/KarmicUpdatesOnShutdown

  • 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

SoftwareUpdates (last edited 2019-04-14 16:59:44 by mpt)