Confirmed users
2,959
edits
Release Management/FirefoxOS/Release Milestones: Difference between revisions
Release Management/FirefoxOS/Release Milestones (view source)
Revision as of 20:19, 7 May 2014
, 7 May 2014→Feature Landing Criteria
| Line 6: | Line 6: | ||
Feature Landing (FL) is a fixed milestone in the release schedule. All feature work must be complete by the FL date. | Feature Landing (FL) is a fixed milestone in the release schedule. All feature work must be complete by the FL date. | ||
=== Feature Landing Criteria === | === Feature Landing Criteria === | ||
* Passes functional testing necessary to meet user story acceptance criteria | * QA signoff | ||
* Features must not land with device automated tests disabled | ** Passes functional testing necessary to meet user story acceptance criteria | ||
* No | ** Features must not land with device automated tests disabled | ||
** No smoketest regressions | |||
* No performance or checkerboarding regressions | |||
* Includes integration/unit tests | * Includes integration/unit tests | ||
* Performance/stability metrics maintained at least on par with previous release | * Performance/stability metrics maintained at least on par with previous release | ||
| Line 19: | Line 21: | ||
* Partial landing of a feature may be acceptable | * Partial landing of a feature may be acceptable | ||
** Feature scope change must be signed off by stakeholders including product, UX and QA (may also include other teams like security) | ** Feature scope change must be signed off by stakeholders including product, UX and QA (may also include other teams like security) | ||
=== What if a feature misses the Feature Landing date? === | === What if a feature misses the Feature Landing date? === | ||
* By default the feature is de-scoped from the release and deferred to the next release | * By default the feature is de-scoped from the release and deferred to the next release | ||