Channels
2830
Comment: no 'devel' channel for ubuntu-developer, we don't want to spend the QA effort on promoting this
|
2829
grammar
|
Deletions are marked like this. | Additions are marked like this. |
Line 42: | Line 42: |
Manually promoted images that reach end-user devices. This is the channels that should be used for everyday use phones. The bq-aquaris.en channel is also the channel which all commercial BQ devices are flashed from. | Manually promoted images that reach end-user devices. This is the channel that should be used for everyday use phones. The bq-aquaris.en channel is also the channel which all commercial BQ devices are flashed from. |
Summary
This page tries to list and explain all available Ubuntu Touch channels that have been currently set-up. Please remember that this information can get quickly out-of-date. All the refactored channels follow the schema specified in Touch/ChannelSchemaSpec - please read this document to understand the rationale for the following setup.
Current Channel List
ubuntu-touch/rc-proposed/*
Automatically built images that are candidates for the rc and later the stable channels; these are currently built from ubuntu/vivid + stable-phone-overlay PPA. RC promotion evaluation in general happens twice a month.
ubuntu-touch/rc-proposed/ubuntu - channel with the community custom tarball
ubuntu-touch/rc-proposed/bq-aquaris.en - channel with the BQ custom tarball
ubuntu-touch/rc-proposed/bq-aquaris.en-proposed - channel for testing of new custom tarballs before upload
ubuntu-touch/rc/*
Manually promoted images from ubuntu-touch/rc-proposed/*. An image from this channel once per month gets promoted to the stable channel as the new official OTA.
ubuntu-touch/rc/ubuntu
ubuntu-touch/rc/bq-aquaris.en
ubuntu-touch/rc/ubuntu-developer - channel with a developer-oriented custom tarball, including extra payload useful for app-developers
ubuntu-touch/devel-proposed/*
Automatically built images from the latest devel series (currently ubuntu/wily). This is the channel that has the latest bleeding-edge development, absolutely no guarantee of stability.
ubuntu-touch/devel-proposed/ubuntu - devel channel with the community custom tarball
ubuntu-touch/devel-proposed/krillin.en - devel channel with the BQ custom tarball (will be renamed to bq-aquaris.en)
ubuntu-touch/devel-proposed/krillin.en-proposed - devel channel for testing of new custom tarballs before upload (will be renamed to bq-aquaris.en-proposed)
ubuntu-touch/devel-proposed/ubuntu-developer - devel channel with a developer-oriented custom tarball, including extra payload useful for app-developers
ubuntu-touch/devel/*
Manually promoted images from ubuntu-touch/devel-proposed/*. Promotions do not follow any specific schedules.
ubuntu-touch/devel/ubuntu
ubuntu-touch/devel/krillin.en - (will be renamed to bq-aquaris.en)
ubuntu-touch/stable/*
Manually promoted images that reach end-user devices. This is the channel that should be used for everyday use phones. The bq-aquaris.en channel is also the channel which all commercial BQ devices are flashed from.
ubuntu-touch/stable/ubuntu
ubuntu-touch/stable/bq-aquaris.en
ubuntu-touch/stable/ubuntu-developer
Touch/Channels (last edited 2015-11-17 18:47:07 by pool-72-84-88-96)