AMO/FlightDeck: Difference between revisions

From MozillaWiki
< AMO
Jump to navigation Jump to search
 
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
= Add-ons Builder: End of Life April 2014 =
See https://blog.mozilla.org/addons/2013/12/18/add-on-builder/
= Add-ons Builder: The Mission =
= 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.
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.
Line 21: Line 25:
* Lead Server-side Developer: Piotr Zalewa (zalun) - pzalewa@mozilla.com
* Lead Server-side Developer: Piotr Zalewa (zalun) - pzalewa@mozilla.com
* Lead Client-side Developer: Sean McArthur (seanmonstar) - smcarthur@mozilla.com
* Lead Client-side Developer: Sean McArthur (seanmonstar) - smcarthur@mozilla.com
* Search and Services: Arron Schaar
* Search and Services: Arron Schaar (arron) - aschaar@mozilla.com
* Developer Manager: Wil Clouser (clouserw)
* Developer Manager: Wil Clouser (clouserw)


Line 45: Line 49:
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)
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)


*[https://docs.google.com/document/d/18eDIEe4_sObwe_e71WWWL-izwBcR0xhyik1oB-y6fWA/edit?hl=en_US&authkey=CIO1p7YP Product Roadmap DRAFT Q3 2011 - Q4 2012]
* [https://wiki.mozilla.org/AMO/FlightDeck/Roadmap Product Roadmap FINAL Q3 2011 - Q4 2012] - DEPRECATED
 
* [https://wiki.mozilla.org/AMO/FlightDeck/Roadmap/2012 2012 Product Roadmap (FINAL)]
*[https://wiki.mozilla.org/AMO/FlightDeck/Roadmap Product Roadmap FINAL Q3 2011 - Q4 2012]


=== Feature Pages ===
=== Feature Pages ===
* [[AMO/FlightDeck/Feature_Pages/Repacker|Add-on Repackaging Service]]
* [[AMO/FlightDeck/Feature_Pages/Repacker|Add-on Repackaging Service]]
=== Release Process ===
<b>Add-on Builder</b>
* 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.
<b>Add-on Repacker Runs</b>
* 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 beta phase of code verification.
* The repacker will only repackage 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.
* A link to the repacked add-ons on the AMO development servers will be posted so add-ons devs have a chance to check and verify the repack of their add-on was successful.
* Upon verification by the two parties above, 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 ==
== Meeting Notes ==

Latest revision as of 20:16, 1 February 2014

Add-ons Builder: End of Life April 2014

See https://blog.mozilla.org/addons/2013/12/18/add-on-builder/

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 (arron) - aschaar@mozilla.com
  • 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

Revision Control System

Git-workflow.png

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)

Feature Pages

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 beta phase of code verification.
  • The repacker will only repackage 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.
  • A link to the repacked add-ons on the AMO development servers will be posted so add-ons devs have a chance to check and verify the repack of their add-on was successful.
  • Upon verification by the two parties above, 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

Documentation

http://flightdeck.readthedocs.org/

Retrieved from "https://wiki.mozilla.org/index.php?title=AMO/FlightDeck&oldid=913192"