ChannelSchemaSpec
Revision 2 as of 2015-03-05 05:25:57
Clear message
Table of Contents |
Summary
The image-based updates server makes it possible to produce a large number of distinct channels for different purposes. However, experience shows that once created, this proliferation of channels becomes very difficult to manage. This document is a proposed method for managing the combinatoric explosion of possible channels.
Multiple axes
Update frequency / maturity
One element that should continue to be represented as different channels is the maturity and/or update frequency of the images. There are currently four levels of maturity:
- devel-proposed: images land in this channel as soon as they are produced and have not been validated.
- devel: images are copied into this channel from devel-proposed only once verified by QA. No limits on update frequency.
- rc: images are copied to this channel from devel after a more rigorous QA process, twice a month.
- stable: identical to the rc channel, but images are only copied to this channel once a month to limit the frequency with which updates are pushed to end users.
Carrier-specific "custom" tarball