|
|
| Line 33: |
Line 33: |
| '''Description''' | | '''Description''' |
|
| |
|
| In its first publicized release, the Add-on Builder will be launched as a website under the AMO domain. The application will undergo hardening and extensive triage during the month of January. In parallel, we will be working with Marketing and PR to generating a marketing plan that targets a much broader audience of developers from those who have never developed an add-on to those who do it professionally.
| | Morph the Add-on Builder into a more general platform for web-centric development that caters to the unique needs of the Add-on SDK team and the Apps team, without hard-coding the Builder to those use-cases. The app will be retooled to leverage/dog-food various systems, conventions, and pluggable code libraries that have been deployed by teams across the organization, this includes the open web app platform, Orion editor, dev tools, etc. |
| | |
| When the Add-on Builder team, and associated stakeholders, agree the product has reached a 1.0 launch-ready state, we will solidify a launch date (initial target is mid February), and begin executing our marketing plan.
| |
| | |
| The team will reserve the entire week following the launch to monitor the product. During this post-launch monitoring period, all members of the primary Builder team will be on-call to address any issues that may arise.
| |
|
| |
|
| '''Goals & Actions''' | | '''Goals & Actions''' |
| Line 54: |
Line 50: |
| '''Description''' | | '''Description''' |
|
| |
|
| In its first publicized release, the Add-on Builder will be launched as a website under the AMO domain. The application will undergo hardening and extensive triage during the month of January. In parallel, we will be working with Marketing and PR to generating a marketing plan that targets a much broader audience of developers from those who have never developed an add-on to those who do it professionally.
| | This final period in 2012 will be dedicated to testing the appified Builder and preparing a marketing plan for our public launch with a UI presence in Firefox. Testing for this release will also include a more detailed security review and additional layers of QA. |
| | |
| When the Add-on Builder team, and associated stakeholders, agree the product has reached a 1.0 launch-ready state, we will solidify a launch date (initial target is mid February), and begin executing our marketing plan.
| |
| | |
| The team will reserve the entire week following the launch to monitor the product. During this post-launch monitoring period, all members of the primary Builder team will be on-call to address any issues that may arise.
| |
|
| |
|
| '''Goals & Actions''' | | '''Goals & Actions''' |