One clarification: On Wed, Oct 29, 2014 at 02:14:05PM -0700, Steve Langasek wrote: > Fixes for specific bugs targeted for our upcoming customer-oriented release > should continue to be landed to ubuntu-rtm/14.09. Anything else that is not > being landed for RTM - e.g., any forward-looking feature work - should be > landed to vivid only.
Note in particular that this means that bugfixes targeted to the OTA-1 or OTA-2 milestones should also be landed *only* to vivid for the time being. The 14.09 channel is only for RTM-targeted bugfixes, until we get a golden image for the RTM milestone and an all-clear from the product management team. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] > Because the base system of vivid continues to move on, we will not be doing > binary syncs between vivid and ubuntu-rtm/14.09. As Ćukasz mentioned in his > mail on Friday, you will continue to be able to request source sync landings > from vivid to ubuntu-rtm/14.09. Of course, this option is only available > so long as the packages are in sync between vivid and ubuntu-rtm/14.09. As > soon as you start to land anything to vivid which is *not* targeted for > 14.09, you will need to create a separate branch for your project and target > any future 14.09 bugfixes to that other branch. > > > There are other plans in the works right now, around rolling forward from > 14.09 to a branch based on Ubuntu 14.10. You should be hearing more from us > on this topic by the end of next week. But in the meantime, the above two > channel families (with corresponding source branches) should be the only > thing you need to worry about for landing your code.
signature.asc
Description: Digital signature
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp

