canmove, Confirmed users, Bureaucrats and Sysops emeriti
6,906
edits
Features/Feature page documentation: Difference between revisions
Jump to navigation
Jump to search
m
→Stage and Status
| Line 15: | Line 15: | ||
* '''Planning''': With the requirements and design clarified and approved, the feature moves into the planning stage, where the Engineering team sorts out the overall technical approach that will be taken, and other stakeholder teams (Security, Privacy, QA, Accessibility, Localization, etc.) have the opportunity to review the feature in detail. This stage is complete when all stakeholder teams finish their reviews and are comfortable with the requirements, design, and plan for implementation. | * '''Planning''': With the requirements and design clarified and approved, the feature moves into the planning stage, where the Engineering team sorts out the overall technical approach that will be taken, and other stakeholder teams (Security, Privacy, QA, Accessibility, Localization, etc.) have the opportunity to review the feature in detail. This stage is complete when all stakeholder teams finish their reviews and are comfortable with the requirements, design, and plan for implementation. | ||
* '''Development''': This is where coding begins and activity for feature development moves into Bugzilla. Detailed progress tracking will not be done on the wiki — that should all happen in Bugzilla, and will not be replicated on the feature pages. Product or project managers are responsible for updating the status on the feature pages if and when needed. | * '''Development''': This is where coding begins and activity for feature development moves into Bugzilla. Detailed progress tracking will not be done on the wiki — that should all happen in Bugzilla, and will not be replicated on the feature pages. Product or project managers are responsible for updating the status on the feature pages if and when needed. | ||
* '''Release''': | * '''Release''': In this stage the team documents the final checklist of everything the team feels should happen before a feature can land. Over time, we’ll develop a standardized checklist for this, but we’ll sort that out as we go. For now, the team will create their own checklist and ensure that everything on it is complete before the feature lands. | ||
* '''Landed''': | * '''Landed''': The feature has landed. | ||
* '''Shipped''': | * '''Shipped''': The feature has been shipped as part of a final product. | ||
* '''Complete''': | * '''Complete''': The feature team has done whatever follow-up or post-mortem work they feel necessary. The end. | ||
=== Release target === | === Release target === | ||