1,273
edits
AMO/FlightDeck: Difference between revisions
→Release Planning and Implementation
Dandonkulous (talk | contribs) |
Dandonkulous (talk | contribs) |
||
| Line 51: | Line 51: | ||
=== Feature Pages === | === Feature Pages === | ||
* [[AMO/FlightDeck/Feature_Pages/Repacker|Add-on Repackaging Service]] | * [[AMO/FlightDeck/Feature_Pages/Repacker|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 == | == Meeting Notes == | ||