Channels

Differences between revisions 9 and 20 (spanning 11 versions)
Revision 9 as of 2015-05-15 16:26:51
Size: 2878
Editor: vorlon
Comment: there is no rc-proposed for the ubuntu-developer image, the team's QA happens on top of rc
Revision 20 as of 2015-11-17 18:47:07
Size: 3264
Editor: dobey
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
== Current Channel List ==
Line 6: Line 7:
== Current Channel List == For a more clear "Recommended Channel" for all devices (currently Nexus 4, Nexus 7, Nexus 10, Bq Aquaris E4.5, Meizu MX4) see https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/

=== ubuntu-touch/stable/* ===

Manually promoted images from ubuntu-touch/rc/* that reach end-user devices. These channels should be used for everyday-use phones. They usually get updated every six weeks. Those updates are the official OTA (over the air) releases.

   * '''ubuntu-touch/stable/ubuntu''' - channel with the community custom tarball
   * '''ubuntu-touch/stable/ubuntu-developer''' - channel with a developer-oriented custom tarball, including extra payload useful for app-developers
   * '''ubuntu-touch/stable/bq-aquaris.en''' - channel used by all commercial BQ devices, contains the BQ custom tarball
   * '''ubuntu-touch/stable/meizu.en'''

=== ubuntu-touch/rc/* ===

Manually promoted images from ubuntu-touch/rc-proposed/*. These channels usually get updated twice a month.

   * '''ubuntu-touch/rc/ubuntu'''
   * '''ubuntu-touch/rc/ubuntu-developer'''
   * '''ubuntu-touch/rc/bq-aquaris.en'''
   * '''ubuntu-touch/rc/meizu.en'''
Line 10: Line 29:
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. 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'''''.
Line 12: Line 31:
   * '''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/ubuntu'''
  * '''ubuntu-touch/rc-proposed/ubuntu-developer'''
   * '''ubuntu-touch/rc-proposed/bq-aquaris.en'''
Line 15: Line 35:

=== 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/rc-proposed/meizu.en'''
   * '''ubuntu-touch/rc-proposed/meizu.en-proposed'''
Line 39: Line 44:
   * '''ubuntu-touch/devel/ubuntu-developer'''    * '''ubuntu-touch/devel/meizu.en'''
Line 41: Line 46:
=== ubuntu-touch/stable/* === === ubuntu-touch/devel-proposed/* ===
Line 43: Line 48:
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. Automatically built images from the latest devel series. This is the channel that has the latest bleeding-edge development, absolutely no guarantee of stability.
Line 45: Line 50:
   * '''ubuntu-touch/stable/ubuntu'''
   * '''ubuntu-touch/stable/bq-aquaris.en'''
   * '''ubuntu-touch/stable/ubuntu-developer'''
   * '''ubuntu-touch/devel-proposed/ubuntu''' - devel channel with the community custom tarball
   * '''ubuntu-touch/devel-proposed/ubuntu-developer''' - devel channel with a developer-oriented custom tarball, including extra payload useful for app-developers
   * '''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/meizu.en'''

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

For a more clear "Recommended Channel" for all devices (currently Nexus 4, Nexus 7, Nexus 10, Bq Aquaris E4.5, Meizu MX4) see https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/

ubuntu-touch/stable/*

Manually promoted images from ubuntu-touch/rc/* that reach end-user devices. These channels should be used for everyday-use phones. They usually get updated every six weeks. Those updates are the official OTA (over the air) releases.

  • ubuntu-touch/stable/ubuntu - channel with the community custom tarball

  • ubuntu-touch/stable/ubuntu-developer - channel with a developer-oriented custom tarball, including extra payload useful for app-developers

  • ubuntu-touch/stable/bq-aquaris.en - channel used by all commercial BQ devices, contains the BQ custom tarball

  • ubuntu-touch/stable/meizu.en

ubuntu-touch/rc/*

Manually promoted images from ubuntu-touch/rc-proposed/*. These channels usually get updated twice a month.

  • ubuntu-touch/rc/ubuntu

  • ubuntu-touch/rc/ubuntu-developer

  • ubuntu-touch/rc/bq-aquaris.en

  • ubuntu-touch/rc/meizu.en

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.

  • ubuntu-touch/rc-proposed/ubuntu

  • ubuntu-touch/rc-proposed/ubuntu-developer

  • ubuntu-touch/rc-proposed/bq-aquaris.en

  • ubuntu-touch/rc-proposed/bq-aquaris.en-proposed - channel for testing of new custom tarballs before upload

  • ubuntu-touch/rc-proposed/meizu.en

  • ubuntu-touch/rc-proposed/meizu.en-proposed

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/devel/meizu.en

ubuntu-touch/devel-proposed/*

Automatically built images from the latest devel series. 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/ubuntu-developer - devel channel with a developer-oriented custom tarball, including extra payload useful for app-developers

  • 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/meizu.en

Touch/Channels (last edited 2015-11-17 18:47:07 by dobey)