Hello, Just wanted to give a quick heads up to everyone for a change that'll happen on Monday (by EOD US/Canada eastern time).
Currently, system-image.ubuntu.com contains the following channels: - daily - daily-proposed The former containing only images that passed automatic and manual validation and intended at end users, the latter containing every single image ever produced and intended mostly for QA testing and image developers. Starting on Monday, the list of channels will become: - devel (alias to saucy) - devel-proposed (alias to saucy-proposed) - devel-customized (alias to saucy-customized) - saucy - saucy-proposed - saucy-customized - stable (alias to saucy) So while that's a pretty long list, we're only moving from 2 channels to 3 channels and adding a bunch of aliases on top. The new channel is saucy-customized and will be mostly identical to saucy except for the addition of a customization tarball used to showcase OEM/carrier customizations of Ubuntu Touch. All the others are aliases, devel-* will always point to the current development series, similar to the devel alias for the Ubuntu archive. The stable alias will point to saucy for now and will keep pointing to saucy until T is released. I'll also manually maintain two transitional aliases until the 24th of September: - daily (alias to devel) - daily-proposed (alias to devel-proposed) Existing users will have until the 24th to apply an over the air update that'll move them to the right target channel, no manual action will be required as long as you run an update before the old names are removed from the server. That also means that anyone maintaining tools that currently use "daily" or "daily-proposed" has until the 24th of September to switch them to "devel" or "devel-proposed", past that date, the affected tools will likely just fail on a 404. On top of those new channels, the image numbering will also change slightly. Currently when an image is fully tested in daily-proposed, it's copied over to daily but then gets assigned a different ID than it had in proposed. That's been causing some confusion that the server update landing on Monday will try to address by keeping those IDs consistent between saucy and saucy-proposed. The main user visible change is that users of saucy (or one of its aliases) may notice gaps in their build IDs as they may currently be on ID 25 with the next one being ID 28 as 26 and 27 didn't pass QA validation and never got released to saucy. There are also a lot of boring server changes that nobody should notice, if those actually affect you, chances are you're doing something wrong, so come talk to me :) If you've got any question about the above, feel free to reply to this e-mail or catch me on IRC. -- Stéphane Graber Ubuntu developer http://www.ubuntu.com
signature.asc
Description: Digital signature
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp