Blueprint changed by Kenny Strawn: Whiteboard changed: * Create a public Launchpad team (say, ~ubuntu-appdev) that isn't moderated and anyone can join * Create a PPA associated with said team (say, ubuntu-appdev/developer-channel) that would be used as the rolling-release LTS-to-LTS channel - * Fork LTS releases off of that channel into another PPA associated with that team (say, ubuntu-appdev/lts-channel) and fix the bugs in them at least 9-12 months ahead of release to make the LTS releases more polished and stable. + * Fork LTS candidate apps off of that channel into another PPA associated with that team (say, ubuntu-appdev/lts-beta) and fix the bugs in them at least 9-12 months ahead of release to make the LTS releases more polished and stable. + * When the LTS packages are ready to submit as new LTS releases, fork them off into yet another PPA (say, ubuntu-appdev/lts-stable) and they'll update on all LTS systems automatically
-- Future releases: Proposal for implementation of separate LTS-to-LTS rolling release channel https://blueprints.launchpad.net/ubuntu/+spec/desktop-x-rolling-release-nonlts-proposal -- Mailing list: https://launchpad.net/~unity-design Post to : unity-design@lists.launchpad.net Unsubscribe : https://launchpad.net/~unity-design More help : https://help.launchpad.net/ListHelp
