AMO/FlightDeck

Add-ons Builder: The Mission

The Add-ons Builder enables rapid, collaborative, community-driven development of add-ons built with the Add-on SDK and third-party libraries that extend the Add-on SDK core with additional APIs and functionality.

Application Instances

Production

• most stable
• always the latest tagged version

Staging

• used primarily in release testing after code freezes
• updated every 15 minutes from staging branch

Trunk

• continuously updated by developers, contains a variety of features from upcoming releases
• updated every 15 minutes from master branch

Production Team

• Product Manager: Daniel Buchner (dbuc) - daniel@mozilla.com
• Lead Server-side Developer: Piotr Zalewa (zalun) - pzalewa@mozilla.com
• Lead Client-side Developer: Sean McArthur (seanmonstar) - smcarthur@mozilla.com
• Search and Services: Arron Schaar
• Developer Manager: Wil Clouser (clouserw)

Addon Builder Helper

This add-on is needed for FlightDeck to fly. The source is locate on Github here: https://github.com/mozilla/addon-builder-helper

Contributions

• Find or create bug in bugzilla (IT bugs here - only use this if you have a good reason. 99% of the time this should go through clouserw)
• How to Contribute succesfully
• Official Github Repo

Revision Control System

• Git hosted on Github
• Code Workflow inspired by this model
• One main repository github.com/mozilla/FlightDeck

Release Planning and Implementation

Roadmap

The linked document below is used for planning and development of specs for upcoming releases of the Add-ons Builder. Once a release spec is finalized on the roadmap, it will transferred to wiki format for quick reference during development cycles. (see the Releases section below)

• Product Roadmap DRAFT Q3 2011 - Q4 2012

• Product Roadmap FINAL Q3 2011 - Q4 2012

Feature Pages

• Add-on Repackaging Service

Release Process

Add-on Builder

• Releases may go out as frequently as once per week, on Wednesday afternoons at 2PM PST
• Prior to release, code will freeze at the beginning of the week on Monday (not withstanding any critical patches we allow)
• The PM will interface with the Developer Manager and IT to ensure the release is properly scheduled.
• Depending on the outcome of QA testing the release can be green-lighted and tagged on Github any time between Monday and Wednesday, but a decision to push must occur at least 1 hour prior to the scheduled release time.
• At the time releases are taking place, all developers are required to be on hand to triage any issues that may arise on live.

Add-on Repacker Runs

• In coordination with the Add-on SDK team, the repacker will begin test runs on the AMO dev site when a new SDK version enters the RC phase of code verification.
• The repacker will repackage all add-ons on AMO that originated from the Add-on Builder
• QA will verify the repacker acted on the right set of add-ons, produced add-ons that operate as expected, and that no errors were thrown in the process from either the repacker code or SDK cfx xpi build loop.
• Upon verification, results will be communicated to the SDK team by the Builder PM. The SDK and Builder teams will examine the results and make a joint decision if and when to begin repackaging add-ons on production.

Meeting Notes

• September 28, 2011
• September 7, 2011
• August 24, 2011
• August 17, 2011
• August 10, 2011
• July 28, 2011
• June 15, 2011
• June 1, 2011
• May 18, 2011
• April 27, 2011
• April 20, 2011
• April 13, 2011
• March 30, 2011
• March 23, 2011
• March 16, 2011
• March 9, 2011
• March 2, 2011
• February 23, 2011
• February 16, 2011
• February 2, 2011
• January 26, 2011
• January 19, 2011
• January 12, 2011
• January 5, 2011
• December 29, 2010
• December 8, 2010
• December 1, 2010
• November 24, 2010
• November 17, 2010

Documentation

http://flightdeck.readthedocs.org/