new-feature-triage.rst (1795B)
1 New Feature Triage 2 ================== 3 4 Identifying Feature Requests 5 ---------------------------- 6 7 Bugs which request new features or enhancements should be of 8 type=\ ``enhancement``. 9 10 Older bugs may also be feature requests if some or all of the following 11 are true: 12 13 - Bugs with ``feature`` or similar in whiteboard or short description 14 - ``[RFE]`` in whiteboard, short description, or description 15 - Bugs not explicitly marked as a feature request, but appear to be 16 feature requests 17 - Bugs marked with ``feature`` keyword 18 19 Initial Triage 20 -------------- 21 22 Staff, contractors, and other contributors looking at new bugs in 23 *Firefox::Untriaged* and *::General* components should consider if a 24 bug, if not marked as a feature request, should be one, and if so: 25 26 - Update the bug’s type to ``enhancement`` 27 - Determine which product and component the bug belongs to and update 28 it **or** 29 30 - Use *needinfo* to ask a component’s triage owner or a module’s 31 owner where the request should go 32 33 Product Manager Triage 34 ---------------------- 35 36 - The product manager for the component reviews bugs of type 37 ``enhancement`` 38 39 - This review should be done a least weekly 40 41 - Reassigns to another Product::Component if necessary **or** 42 - Determines next steps 43 44 - Close bug as ``RESOLVED WONTFIX`` with comment as to why and 45 thanking submitter 46 - If bug is similar enough to work in roadmap, close bug as 47 ``RESOLVED DUPLICATE`` of the feature bug it is similar to 48 49 - If there’s not a feature bug created already, then consider 50 making this bug the feature bug 51 52 - Set type to ``enhancement`` 53 54 - Set bug to ``P5`` priority with comment thanking submitter, and 55 explaining that the request will be considered for future roadmaps