Testing upgrades for pre-installed systems

Registered by Victor Tuson Palau on 2010-10-24

Part of the Ubuntu users are those that buy a pre-install system from a manufacturer (n). In most cases, the manufacturer has been involve with canonical to help system be support from "downloadable" ubuntu for the next release (n+1).

Discussion points:
* Should we validate the upgrade path from pre-installed n to *stock* n+1? If so , who should drive the work?

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
Victor Tuson Palau
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Work items:
 [mvo] automatically popup a information window if the distro goes EOL on a GUI: DONE
 [mvo] automaticall show EOL information in the motd on servers: DONE
 setup wiki/help page explaining about EOL and the options the user has: TODO

Ideal Path for EOL releases is to upgrade to latest LTS, It requires:
*update manager to tell the user that they need to upgrade due to EOL, next steps [MVO]
*automated testing of upgrades in OEM images use for shipping
**in Natty will be basic automated testing - [Victorp]
**need to know what machines are shipping with EOL
*update manager to be able to jump directly to the latest LTS + testing to make sure it works

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.