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