Bugmasters/Projects: Difference between revisions

Jump to navigation Jump to search
m
Line 1: Line 1:
Here are some ongoing Bugmaster projects to help manage Mozilla bugs.  Each one will have bug days or events, to help its contributors work together.  "Triaging" a bug can mean a lot of different things depending on context. In general, it means adding more information to a filed bug.
Here are some ongoing Bugmaster projects to help manage Mozilla bugs.  Each one will have bug days or events, to help its contributors work together.  "Triaging" a bug can mean a lot of different things depending on context. In general, it means adding more information to a filed bug.


==Middle-aged bugs==
This is a project to work on Firefox bugs reported in a range time of -6months(-180d) to -1months(-30d).
These are bugs that haven't been changed recently, but were reported within the last 6 months.
Triaging them may find good, relevant bugs. It can also help clear out invalid bugs!
[https://bugzilla.mozilla.org/buglist.cgi?list_id=7036513&resolution=---&resolution=DUPLICATE&chfieldto=-30d&chfield=[Bug%20creation]&query_format=advanced&chfieldfrom=-180d&bug_status=UNCONFIRMED&component=Untriaged&product=Firefox Middle Aged Untriaged Firefox Bugs], UNCONFIRMED.
<onlyinclude>
<bugzilla>
{
    "product": "Firefox",
    "status": "UNCONFIRMED",
    "include_fields": "id, summary, status, whiteboard",
    "order": "bug_id",
    "changed_before": "-1m",
    "changed_after": "-6m"
}
</bugzilla>
</onlyinclude>
* '''Verify the bug'''
**  verify if the bug is still valid
**  read the description and try to reproduce it on the newest Firefox version
**  add ''need-info'' flag for reporter
*** eg. can you still reproduce the bug?
*** eg. could you provide more info about this?
** ask for whatever additional details you need to understand
* '''Replicate the bug'''
**  if the bug is an enhancement request set the severity flag as ''enhancement''
**  if you cannot reproduce the bug
***  if the reporter doesn't answer 1 week later a requested need-info flag and the bug is INCOMPLETE tag the bug as closeme yyyyMMdd (perhaps 2 weeks later?) and wait for that period before you close it. 
*** if the bug has all the info you need to close it, close as WORKSFORME or INVALID
** if you cannot reproduce the bug and you are on a different OS add a need-replication tag
** if you cannot reproduce the bug, help the reporter in resolving the problem if he/she answers.
** if you can replicate the bug in the newer Firefox Versions
***  comment the bug
*** mark it as NEW
''Remarks''
* If a bug reporter hasn't answered to qa requested added in the first week after he/she reported the bug, they are more likely to be not interested anymore.
* Some of these bugs have more than one comment, maybe those are more likely to be significant and already started to be triaged.


==Mentored Bugs Team==
==Mentored Bugs Team==
Confirmed users
2,822

edits

Navigation menu