ReleaseUpgrades

Differences between revisions 3 and 4
Revision 3 as of 2012-01-27 13:37:51
Size: 1865
Editor: mpt
Comment: + "Calculating the upgrade" (placeholder)
Revision 4 as of 2012-01-27 17:35:12
Size: 2050
Editor: mpt
Comment: + ubuntu-recovery
Deletions are marked like this. Additions are marked like this.
Line 27: Line 27:
 * changing the MBR so a specific key always starts from the recovery partition.  * changing the MBR so a specific key always starts from the recovery partition. ([[https://launchpad.net/ubuntu-recovery|Ubuntu Recovery]] already does this for OEM installations.)
## https://wiki.canonical.com/OEMServices/Engineering/Mainstream/RecoveryInstaller

This is the beginning of a living specification for how Ubuntu should present release upgrades. It is part of Ubuntu’s overall software handling.

  • Packages affected: release-upgrader

Invitation to upgrade

You should be able to upgrade from one of three access points: Software Updater, Ubuntu Software Center, or the Ubuntu installer.

If you choose to upgrade from either Software Updater or Ubuntu Software Center, you should first see an “Upgrade to Ubuntu {new version}” dialog containing information about the new version (bug 885720), the price of “Free”, and “Cancel” and “Upgrade Now” buttons.

upgrade-info.png

Calculating the upgrade

upgrade-info-old.png

Offering backup/recovery

We would like to maximize the proportion of people who can successfully use their computer after attempting an upgrade.

To do that, we would like to offer a simple backup or recovery system (probably not both) that lets people restore/recover from a failed upgrade.

This might involve:

  • inviting people to back up their system files to an external disk or USB key
  • installing a recovery partition on the same disk as is being used for the installation, and writing a minimal disk image there
  • changing the MBR so a specific key always starts from the recovery partition. (Ubuntu Recovery already does this for OEM installations.)

Previous work

Configuration file conflicts

If there is a configuration file conlict during an upgrade, the upgrade process should not ask if you want to replace it. Instead, it should rename the existing file to {filename}.{date}, and install the new file.

ReleaseUpgrades (last edited 2019-10-08 08:37:10 by mpt)