auto-update-blueprint

Differences between revisions 22 and 23
Revision 22 as of 2007-04-17 14:25:10
Size: 4926
Editor: person1
Comment: Formatting+1
Revision 23 as of 2007-04-17 14:35:01
Size: 4766
Editor: person1
Comment:
Deletions are marked like this. Additions are marked like this.
Line 22: Line 22:
Currently there are a few options to "automatically update" ''Ubuntu''. One way being via third party software, and the other, cron-jobs and scripts. Both go away from the "Linux for Human Begins" or "Just Working" attitude. Therefore a solution must be made within the ''Ubuntu'' release which solves the problem, both with stability and easy of use.
Line 25: Line 27:


 * For those users who like to have complete control over their system, they have the ability to turn auto-updates off, and can still update via the normal means.

 * Users who want to be up-to-date without the hassle will have the ability to have all updates downloaded and installed, without any interaction.

 * The users who trust ''Ubuntu'' Security updates, etc. will be able to have security updates downloaded and installed, while still manually installing optional and recommended updates.

 * And the users who want to pick and choice the updates without waiting for them to download, can automatically predownload the updates, so they can be installed later at the users digression.
Line 33: Line 44:

The ''Ubuntu'' update manager should have the ability to automatically install updates when notified by the repositories, of a new update. However, there should be some power in the hands of the user, therefore sane defaults and options must be available, through a carefully created "user-friendly" graphical interface.
Line 53: Line 66:
=== Updates ===

=== Reboots ===

Often time Linux updates will go without any interruptions to the working environment, and hardly need a physical-reboot, however these are rare occasions when such an updates is released.

Users will now have that ability to reboot the PC's while away, after new updates, or automatically reboot at a specified time. If the users choices to have the computer reboot after the installation, a sixty-second warning/prompt should be present to ensure the users is ready for the reboot (if no response is given to the prompt, the computer is rebooted). In addition is the reboot is scheduled, the user should be warned before the reboot. At anytime, a reboot should be able to be canceled.
Line 58: Line 79:

None.
Line 65: Line 88:

== Options ==

Currently there are a few options to "automatically update" ''Ubuntu''. One way being via third party software, and the other, cron-jobs and scripts. Both go away from the "Linux for Human Begins" or "Just Working" attitude. Therefore a solution must be made within the ''Ubuntu'' release which solves the problem, both with stability and easy of use.

== Plan ==

The ''Ubuntu'' update manager should have the ability to automatically install updates when notified by the repositories, of a new update. However, there should be some power in the hands of the user, therefore sane defaults and options must be available, through a carefully created "user-friendly" graphical interface.

These options satisfy the following basic user classes, while its obvious that others will exists, these sane options should provided a solution to all parties.

 - For those users who like to have complete control over their system, they have the ability to turn auto-updates off, and can still update via the normal means.

 - Users who want to be up-to-date without the hassle will have the ability to have all updates downloaded and installed, without any interaction.

 - The users who trust ''Ubuntu'' Security updates, etc. will be able to have security updates downloaded and installed, while still manually installing optional and recommended updates.

 - And the users who want to pick and choice the updates without waiting for them to download, can automatically predownload the updates, so they can be installed later at the users digression.

== Reboots ==

Often time Linux updates will go without any interruptions to the working environment, and hardly need a physical-reboot, however these are rare occasions when such an updates is released.


Users will now that ability to reboot the PC's while away, after new updates, or automatically reboot at a specified time. If the users choices to have the computer reboot after the installation, a sixty-second warning/prompt should be present to ensure the users is ready for the reboot (if no response is given to the prompt, the computer is rebooted). In addition is the reboot is scheduled, the user should be warned before the reboot. At anytime, a reboot should be able to be canceled.

NOTE: Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes.

Summary

The ability to automatically download and install updates (unattended) when they are released. Users will be able to configure their systems, so that updates are automatically handled by the system without interaction.

Rationale

With a vigorously release schedule and round-the-clock updates, Linux is one of the most secure and "well-updated" operating systems in the world. But with this cutting edgy technology comes endless updates. Although this can be seen as a good thing, it can become overly cumbersome and annoying to end-users, simply trying to do their work, without tinkering with the underlying OS.

Currently Ubuntu makes updates fun and easy, with the notifications in the task bar. This icon notifies the user of updates, and allows them to view, download, and install the updates with very few clicks of the mouse, or interruption of current work. Although this is a great asset to updates and the Ubuntu system, there are other routes that can be taken with updates.

Currently there are a few options to "automatically update" Ubuntu. One way being via third party software, and the other, cron-jobs and scripts. Both go away from the "Linux for Human Begins" or "Just Working" attitude. Therefore a solution must be made within the Ubuntu release which solves the problem, both with stability and easy of use.

Thus the role of automatic updates, with the ability to setup the computer to just "download, update, and work", users will be able to continue working uninterrupted, while always being up-to-date and current.

Use cases

  • For those users who like to have complete control over their system, they have the ability to turn auto-updates off, and can still update via the normal means.
  • Users who want to be up-to-date without the hassle will have the ability to have all updates downloaded and installed, without any interaction.
  • The users who trust Ubuntu Security updates, etc. will be able to have security updates downloaded and installed, while still manually installing optional and recommended updates.

  • And the users who want to pick and choice the updates without waiting for them to download, can automatically predownload the updates, so they can be installed later at the users digression.

Scope

This spec requires updates in:

  • - Update Manager

    - Possible apt for better update handling

Design

The Ubuntu update manager should have the ability to automatically install updates when notified by the repositories, of a new update. However, there should be some power in the hands of the user, therefore sane defaults and options must be available, through a carefully created "user-friendly" graphical interface.

Updates

The following options should be present:

  • Automatic Updates Off
  • Automatically Download and Install all Updates
  • Automatically Download and Install Security Updates Only [Recommended]
  • Automatically Download Updates Only (Do not Install)

Reboots

The follow options, will handle auto-reboots:

  • Automatic Reboots Off
  • Automatically Reboot (After the updates are installed) [Recommended]
  • Scheduled Reboot (HH : MM)(AM/PM)

Design Rationale

Updates

Reboots

Often time Linux updates will go without any interruptions to the working environment, and hardly need a physical-reboot, however these are rare occasions when such an updates is released.

Users will now have that ability to reboot the PC's while away, after new updates, or automatically reboot at a specified time. If the users choices to have the computer reboot after the installation, a sixty-second warning/prompt should be present to ensure the users is ready for the reboot (if no response is given to the prompt, the computer is rebooted). In addition is the reboot is scheduled, the user should be warned before the reboot. At anytime, a reboot should be able to be canceled.

Final decision

This is to be determined, after approval.

Outstanding issues

None.

BoF agenda and discussion

This is to be determined, after approval.


CategorySpec

auto-update-blueprint (last edited 2008-08-06 16:27:03 by localhost)