Confirmed users
976
edits
Release Management/FirefoxOS/Release Milestones: Difference between revisions
Release Management/FirefoxOS/Release Milestones (view source)
Revision as of 00:51, 25 April 2014
, 25 April 2014→What if a feature misses the Feature Landing date?
No edit summary |
|||
| Line 19: | Line 19: | ||
* 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 | ||
* Exceptions can be granted based on criteria such as business need, % feature work completed and expected delivery date, and risk of backing out or preffing off. | * Exceptions can be granted based on criteria such as business need, % feature work completed and expected delivery date, and risk of backing out or preffing off. | ||
* 1-2 weeks before the FL date the EPMs will prepare the list of outstanding features and the release manager, release owner, a product rep, and a QA rep will review the outstanding feature list and make a decision about whether each feature that is at risk of missing FL will remain in the target release or be de-scoped | * 1-2 weeks before the FL date the Engineering Project Mangers (EPMs) will prepare the list of outstanding features and the release manager, release owner, a product rep, and a QA rep will review the outstanding feature list and make a decision about whether each feature that is at risk of missing FL will remain in the target release or be de-scoped | ||
** Acceptance of a late feature delivery may come with conditions such as a target landing date and restrictions to the number of string changes | ** Acceptance of a late feature delivery may come with conditions such as a target landing date and restrictions to the number of string changes | ||
** All features that are to land after FL must first land on master/mozilla-central and have QA sign off on uplift | ** All features that are to land after FL must first land on master/mozilla-central and have QA sign off on uplift | ||
== FEATURE COMPLETE (FC) == | == FEATURE COMPLETE (FC) == | ||
The Feature Complete (FC) milestone marks the hard cut off date for all feature work related to the current release. In order to declare FC, QA must have completed a set level of testing. Declaring FC indicates the build is ready for chipset vendors to start chipset related testing. FC is a flexible milestone with a target date. FC will only be declared when all of the FC criteria have been met. | The Feature Complete (FC) milestone marks the hard cut off date for all feature work related to the current release. In order to declare FC, QA must have completed a set level of testing. Declaring FC indicates the build is ready for chipset vendors to start chipset related testing. FC is a flexible milestone with a target date. FC will only be declared when all of the FC criteria have been met. | ||