Features/Lifecycle of a feature: Difference between revisions

Features/Lifecycle of a feature (view source)

424 bytes added , 10 May 2011

m

canmove, Confirmed users, Bureaucrats and Sysops emeriti

6,906

edits

@@ Line 25: / Line 25: @@
 ## Status table, including Feature name, current status ("Not started." is fine if true), and your name as the "Owner" for now.
 ## Summary: should be succinct, but should include enough information and detail that the Features triage team will know what you're proposing and how to prioritize it against other work.  Shouldn't be massive, but should be more than a sentence.  Please ''do not just link to a bug'' and leave it at that -- take the time to summarize and explain it.
-## Team list: Fill in as much of this as you can, but we'll revisit this later.
+## Use cases: both user-facing and developer-facing features must have use cases defined before a Feature is submitted to the Inbox, as this is how the Product Team knows what your feature is about and figures out how it should be prioritized.  If you do not include use cases in the initial Feature page write up, your Feature will be bounced back to you until you include them.
+## Team list: Fill out as much of this as you can, and make sure that the people on the list know that they're on the list.
 ## Anything else you can fill out in the page would be great, but doesn't have to be done at this point.
 # Add your Feature to the [[Features/Inbox|}Features Inbox]].