Update policies for clients tied to network services

Registered by Steve Langasek on 2011-05-06

Many packages in Ubuntu exist to interface with network-based services, whose protocols and features change over time. Services that try to be good citizens with respect to Ubuntu clients, such as Ubuntu One, are left at a disadvantage because they must support the client that was current at the time the oldest supported version of Ubuntu was released. This prevents them being able to provide feature parity for all Ubuntu users, and also impacts their ability to deprecate old protocols in a timely manner.

Can Ubuntu provide a procedure for official updates for network clients that addresses these issues? What should that procedure be?

Blueprint information

Status:
Started
Approver:
None
Priority:
High
Drafter:
None
Direction:
Needs approval
Assignee:
John Lenton
Definition:
Discussion
Series goal:
Accepted for oneiric
Implementation:
Slow progress
Milestone target:
milestone icon oneiric-alpha-3
Started by
Joshua Hoover on 2011-06-24

Related branches

Sprints

Whiteboard

Work items for oneiric-alpha-2:
[chipaca] Get buy-in/approval from release team for new update/delivery mechanism: INPROGRESS

Notes at: http://summit.ubuntu.com/uds-o/meeting/foundations-o-updates-for-network-clients/

ScottK comment 6/16/11:
It's probably the tech board that needs to review this. We've done this before for Landscape. See https://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-March/000550.html and https://wiki.ubuntu.com/LandscapeUpdates

(?)

Work Items