Firefox/Features/ChannelSwitching/Engagement Support

Rapid Release Background:

Goal:

Create website collateral to support the new release channels that will be opened to help us test the next versions of firefox.

Four Channels

We will have four channels, with builds developed for 6 weeks per channel before moving on to the next phase of development:

1. Nightly channel :

This channel is expected to be pretty similar to the current nightly channel. The builds here will be pretty unstable, and we're hoping to eventually have 100K users testing builds "nightly".

2. Aurora channel :

This is a brand new channel that will be more stable than nightlies, think of the stability we experienced with betas 1-7 with Fx 4. This is where we hope to get in-depth testing of features--a lot of features will land here for new versions of firefox, but not all will make it. We want to eventually have 1MM users on this channel.

3. Beta channel:

This is the channel where features should be set. It should be as stable as what we experienced in betas 8-12 of Fx 4 dev process. This channel is for more mainstream users and we hope to have 10MM users on this channel eventually.

4. Release :

This is the channel where we release finished products--so basically the standard we reached for Fx 4.

General Project Tracking :

You can follow along with general project status in bug 646236

Engagement Project background:

We currently have the nightly builds working with our traditional audience. We will be opening up the Aurora channel and builds on April 12th. In order to support that release we need to create a few pieces of collateral and a page to help us start growing our newsletter audience. I am calling this phase 1. We expect the beta channel to open up on or around may 3rd and we need collateral to support that release. This is what I am calling phase 2.

Upcoming Releases

<u</u>

General Projects

• General Tracking Bug
  • Bug 663470
    

Product

• Product - Channel Branding
  • Bug 656518
    

Websites

• Redirect Links to /firefox/channel -[COMPLETE]
  
  • Bug 656645

• Channel Page - Branding Redesign
  
  • Bug 663460
    

• Add "Future Releases" link under desktop & mobile header button in blog.mozilla.com/futurereleases/
  
  • Bug 663759
    

• Add "Future Releases" link under mobile header button in moz.com
  • Bug 663757
    

Promotions

• Billboard Update to Promote Aurora to Firefox 4 Beta Users
  • Bug 661009

• Localize Billboard Update to Promote Aurora to Firefox 4 Beta Users
  • Bug 653323

• Copy Request: Promote Aurora Snippet Series
  • Bug 661310

• Implement Snippets: Promote Aurora Snippet Series
  • Bug 661311

• Copy Request: Promote Beta Snippet Series
  • Bug 661342

• Implement Snippets: Promote Beta Snippet Series
  • Bug 661342

• Copy Request: Promote Beta for Mobile Snippet Series
  • Bug 661345

• Implement Snippets: Promote Beta for Mobile Snippet Series
  • Bug 661379

Upcoming Releases:

• Nightly
  
• Aurora 5.0 - (April 12) - [COMPLETE]
  
• Beta 5.0b1 - [COMPLETE]
  
• Beta 5.0b2 -  (May 17) - [COMPLETE]
  
• Mobile Beta Release - (May 17) - [COMPLETE]
  
• Aurora 6.0 -  (May 24) - [COMPLETE]
  
• Aurora 7.0 & Beta 6.0 (July 5)
  • Aurora 7 & Beta 8 Tracking Bug
    • Bug 662999
• Aurora 8.0 & Beta 7.0 (August 15)
• Aurora 9.0 & Beta 8.0
  

Ongoing Discussions:

• FAQ Page for upcoming Beta releases

need to open bug

link from channel page

• FAQ page for upcoming Aurora Releases

need to open bug

link from channel page

• Blog Strategy
• Release Notes
• Branding and Wordmarks
  

FILE BUGS TO FIX

general security bug: Bug 656662

no html characters are used within blog titles. If they are used they could distort the html rendering of the page Bug 657072

no untrusted users would be allowed to create posts or set blog titles since they could include arbitrary html that could harm the users. Bug 657075