ChannelSwitching/ChannelSwitchingFeature

Feature	Status	ETA	Owner
Means by which users on our new Experimental, Beta and Final channels can switch the channel they are on.	Backend work almost complete - waiting on review. UI Design finished but need to implement.	2011-04-18 (hopefully sooner)	Sheila Mooney

Summary

In order to support our new shorter release cycle, we need a mechanism by which users can switch what channel they are to get on that update path. This applies to users who are on the experimental (new), beta and final channels.

The nightly channel is a separate path and they will continue to receive the nightly updates for mozilla-central. In order for those users to get on a different channel ie: beta, they must first download a beta build.

Implementation includes some back end work as well as minimal front-end UI for doing the switching.

Release Requirements

• Both the front-end and backend pieces need to be implemented and linked together.
• We need to have the experimental channel setup so we can test this.
• We can potentially test this without having the experimental channel in place - we can add a config value so we can switch to the nightly channel just to test the mechanism.

Next Steps

A team is tracking this work during weekly meetings on Wed @10:00am.

Most of the backend implementation is complete. The UI design work is done and we are waiting on the front-end development.

The team is currently working out a plan for how to evangelize the new channels, migrate users, messaging and how this coordinates with any backend work.

Related Bugs & Dependencies

There are 2 main bugs tracking this work...

• https://bugzilla.mozilla.org/show_bug.cgi?id=644517
• https://bugzilla.mozilla.org/show_bug.cgi?id=386760

Team

• Rob Strong - updater change and will work with releng
• Nick Thomas is probably the right person from releng
• Limi - UI design
• Laura and Mayumi on the marketing side
• Rob Sayre - engineering - owner of new release process
• Christian - release management
• Sheila - PM

The team meets weekly on Wed @10:00am in Zombocom.

Designs

Design details and mockups can be found this in this [ https://bugzilla.mozilla.org/show_bug.cgi?id=6445170 bug]

Goals/Use Cases

The high level goals for the feature (which the release requirements checklist should fulfill). These are the guiding light and overall vision for the feature. Refer to this if there is confusion or are disputes about direction, designs, planning, etc.

Non-Goals

Things we are specifically not doing or building as part of this feature.

Other Documentation

Can include things like:

• Competitive landscape
• Research & references
• Whatever else is useful to the project.

Categories TBD.