Bugmasters/Projects: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (Redirected page to Bugmasters#Projects)
 
(83 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Here are some ongoing Bugmaster projects to help manage Mozilla bugs.  Each one will have bug days or events occasionally, to help its contributors communicate and work together.  "Triaging" a bug can mean a lot of different things depending on context, but in general it means adding more information to a filed bug.
#REDIRECT [[Bugmasters#Projects]]
 
((Make separate pages for each project. Add a section for people to sign up on each team with a bugzilla name and link to Mozillians profile...)
 
First: sign up for a Bugzilla account
Second: make a Mozillians account and tag yourself "bugmasters" and "triage"
 
 
==Websites Team==
This is for bugs that have been reported in Mozilla-run websites. It is probably the easiest group of bugs to confirm, so it's a good starting point!
 
* Take a look at the [https://bugzilla.mozilla.org/buglist.cgi?list_id=6185685&resolution=---&resolution=DUPLICATE&query_format=advanced&bug_status=UNCONFIRMED&product=Websites Website UNCONFIRMED] bugs.
* Sort on Status, ID, or another field.
* Check to see that the bug still exists.
* You may want to check it on both the current Firefox version and the Nightly build.
** If you can't reproduce it, ask the reporter, in a comment with a need-info flag, if they can reproduce it.
*** If they can't, or don't answer after a week or so, resolve the bug as WORKSFORME.
** If you can reproduce it, mark it NEW and leave a comment to describe what you did. You may be able to find a person to cc on the bug if you look for who has resolved past, similar bugs.
 
* Websites bugs marked NEW can also use triaging! Here's a bugzilla query for [https://bugzilla.mozilla.org/buglist.cgi?list_id=6185727&resolution=---&resolution=DUPLICATE&chfieldto=Now&chfield=[Bug%20creation]&query_format=advanced&chfieldfrom=-1y&bug_status=NEW&product=Websites Website NEW bugs reported within the last year].
 
==Firefox UNCONFIRMED Team==
[https://bugzilla.mozilla.org/buglist.cgi?list_id=6184146&resolution=---&resolution=DUPLICATE&chfieldto=Now&chfield=[Bug%20creation]&query_format=advanced&chfieldfrom=-60d&bug_status=UNCONFIRMED&component=Untriaged&product=Firefox Latest Untriaged Firefox bugs], UNCONFIRMED, from the last 60 days.
 
You may want to edit your search, limiting it to only the operating systems you can test.
 
* '''Understand the bug'''
** Read the description and comments in the bug to understand the problem.
** If you don't understand the bug
*** Comment, add need-info flag for reporter.
*** Ask for whatever additional details you need to understand.
 
* '''Check if it's a duplicate'''
** Search on similar terms in Bugzilla to see if it is a duplicate of another bug.
** (How to search)
** (How to tell if it's a likely dup)
** Tag it dupeme? if you're not sure, and move on.
 
* '''Check if it's a support question'''
** If it's a support question (often malware, FF is slow reports)
** Nicely let the reporter know where to look for the answer or for help.
** Ask the reporter with a need-info flag to resolve the bug as invalid, or resolve it yourself.
 
* '''Test case, if needed'''
** If this bug needs a test case and you don't have one:
** Ask the reporter for one. That might mean simplest or reduced test case code, or a URL.
** Or you could generate a test case and attach it.
 
* '''Replicate the bug'''
** Can you replicate the bug? In the same OS?
** If you can replicated it, and no one else has, leave a comment.
** If you can't replicate it, and are in the same OS
** Ask the reporter with need-info if they still see the issue
*** (Especially if it's an older bug and we're on a new version of FF now)
*** If they don't you can resolve it WORKSFORME or ask reporter to do so
*** If they still see the bug, tag it needs-replication
** If you can't replicated it and are in a different OS
*** Comment
*** tag it needs-replication
 
* Safe mode, plugins off, New profile
** In some cases (but not all) you may want to ask the bug reporter if they still see the bug in safe mode (with all plugins disabled) and with a new profile.
** (((Explain when and when perhaps not to do this)))
 
* IF you can replicate the bug, and it's likely to be a Firefox bug (not a bug with a plugin, etc)
** Comment that you replicated the bug
** Mark it NEW
** You can keep adding info to the bug if you think it will be useful.
 
==Incoming Team==
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Today%27s%20UNCO%20Bugs&list_id=6184210 Bugs Filed Today]. All bugs filed in the last 24 hours.  Usually this is around 400 bugs, but the number fluctuates over the course of the day.
 
To work in this area, go through the bugs with status UNCONFIRMED.
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Today%27s%20UNCO%20Bugs&list_id=6184175 Today's UNCO Bugs]
** If you can reproduce a bug, and are fairly sure it is a Mozilla bug, mark it NEW.
** Assign the bug into a product and component, or tag it needs-component
** Tag the bug with other triage tasks that may be needed.
 
 
 
==Nightly build bug team==
Hello! If you'd like to help out with bug management for Nightly builds, please email [mailto:bugmaster@mozilla.com bugmaster@mozilla.com]!
 
Every night the [http://www.mozilla.org/projects/firefox/prerelease.html latest pre-release version of Firefox] is made available. If you want to test against the cutting edge of Firefox, [http://nightly.mozilla.org/ download the Nightly build] and use it as your main browser. If you find any bugs, file them. ([[How to File a Bug]]).
 
You may also be interested in looking at the bugs others have filed, and see if you can replicate them or add any useful information. Triaging the Nightly bugs will help us catch important bugs as quickly as possible!
 
1. Download the Nightly build and run it.<br>
2. Make a bugzilla account.<br>
3. Skim over the [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=DUPLICATE&query_format=advanced&version=23%20Branch&product=Firefox&list_id=6391547 current bugs against the Nightly release] (currently, 23 build).<br>
4. File bugs when you find them.<br>
5. Triage through the list of Nightly bugs. So helpful!<br>
--- replicate the bug, comment, and confirm it<br>
--- needinfo the bug reporter to get more details<br>
--- regression testing with the [http://mozilla.github.io/mozregression/ mozregression] tool<br>
<br>
 
For example, the current released version of Firefox is 20.0. The [http://www.mozilla.org/en-US/firefox/channel/ Beta] version is 21, and the Aurora version is 22. That means the Nightly build is 23. The bugs filed against that release are listed as being in the [https://bugzilla.mozilla.org/buglist.cgi?list_id=6375630&resolution=---&resolution=DUPLICATE&query_format=advanced&version=23%20Branch&product=Firefox 23 branch] of Firefox. 
 
* To search later branches, go to the [https://bugzilla.mozilla.org/query.cgi?query_format=advanced Advanced Search form] in Bugzilla, select Firefox for the product, then under the Detailed Bug Information dropdown, scroll through the Versions listed and select the latest one. That search will bring up all bugs reported for the latest nightly build.
 
* More explanation of the release channels for Firefox:
** https://wiki.mozilla.org/Features/Release_Tracking
** https://blog.mozilla.org/channels/2011/07/18/every-six-weeks/
 
==Aurora bug triage team==
==Nightly build bug team==
Hello! If you'd like to help out with bug management for Aurora builds, please email [mailto:bugmaster@mozilla.com bugmaster@mozilla.com]!
 
Every night the [http://www.mozilla.org/projects/firefox/prerelease.html latest pre-release version of Firefox] is made available as the Nightly release. After 6 weeks of further development that branch becomes the Aurora release, and is more stable than the nightly. If you want to test against the Aurora release of Firefox, [http://www.mozilla.org/en-US/firefox/channel/#aurora download the Aurora build] and use it as your main browser. If you find any bugs, file them. ([[How to File a Bug]]).
 
You may also be interested in looking at the bugs others have filed, and see if you can replicate them or add any useful information. Triaging the Aurora bugs will help us catch important bugs quickly, while you still have a relatively stable development browser to use!
 
1. Download the Aurora build and run it.<br>
2. Make a bugzilla account.<br>
3. Skim over the [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=DUPLICATE&query_format=advanced&version=22%20Branch&product=Firefox&list_id=6391547 current bugs against the Aurora release] (currently, the 22 branch).<br>
4. File bugs when you find them...<br>
5. Triage through the list of Aurora bugs. So helpful!<br>
--- replicate, comment, confirm<br>
--- needinfo the bug reporter to get more details<br>
--- regression testing<br>
<br>
 
==Mentored Bugs Team==
 
Many developers tag bugs as good first bugs, or as mentored bugs. Some are tagged with both. Currently, mentored bugs feed the [http://www.joshmatthews.net/bugsahoy/ Bugs Ahoy] site.
Good first bugs feed into [https://openhatch.org/search/?q=Mozilla openhatch.org] . (out of date)
 
Help maintain this list for contributors who are new to Mozilla development!
 
* Is the bug old and stale?
** Should it be closed?
** needinfo on the reporter, or mentor, or assignee?
* Is the bug current, and assigned, but the assignee hasn't touched it for a couple of weeks?
** needinfo the assignee to ask nicely if they're still working on it or intending to
** If the reporter hasn't touched the bug in a month, unassign it
 
* Triage through bugs that have the whiteboard flag [good first bug] but NOT the mentor= flag.
** [https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&list_id=6500843&o1=casesubstring&resolution=---&resolution=DUPLICATE&status_whiteboard_type=allwordssubstr&query_format=advanced&status_whiteboard=good%20first%20bug&v1=mentor good first bugs query] (no mentor)
 
* Triaging strategies:
** Sort the list by component.
*** Pick a particular product and component. Talk with the bugzilla owner of that component or the module owner.
** Sort the list by ID. It's good to check up on very old bugs with a low ID number.
** Sort the list by last changed. For bugs that haven't been touched in weeks or months, look if they're assigned and ask the assignee, by commenting with the needinfo flag, if they're still working on it.
 
 
* Triage through the bugs that have "mentor=" as a whiteboard flag.
 
* Triage through bugs that have "good first bug" AND "mentor" in the whiteboard flags.
** should they have both?
 
TODO:
* write up how to check on good first bugs
* write up how to choose and tag good first bugs/mentored bugs, and link
 
==Accessibility Triage Team==
This is for bug wranglers who would like to help accessibility developers and end users.
 
* Join #bugmasters and #accessibility
 
* Meta bug cleanup: this is a very easy task for beginners!
** Look at accessibility meta bugs
** Pick one, search for other bugs that are missing, and add them to the meta bug
 
==Core:Layout Triage Team==
This is a good triage task for front-end developers. Help us go through UNCONFIRMED Core:Layout bugs, talk with the bug reporters, replicate the bugs, and attached reduced test cases.
 
The hardest part about layout bug triage is being able to tell apart "is a valid bug" and "is not a valid bug". This typically involves understanding the spec well enough to understand what behavior it requires.  It also typically involves reducing the testcase enough that it's possible to try to figure out what parts of the spec are relevant. The really rare skill here is this ability to reduce testcases well. Here are some useful [http://people.mozilla.org/~mwargers/presentations/creating_a_dom_layout_test.odp slides that explain how to create reduced testcases].
 
* [https://bugzilla.mozilla.org/buglist.cgi?f1=OP&list_id=6456764&f0=OP&o2=substring&f4=CP&query_format=advanced&j1=OR&f3=CP&f2=component&bug_status=UNCONFIRMED&component=Layout&v2=layout&product=Core UNCONFIRMED Core::Layout bugs]
* Sort the list different ways and look over it.
* Pick a bug and read through it and its comments to thoroughly understand it.
* Is the bug reproducible?
* It may be UNCONFIRMED because it is not clear whether a reproducible issue is a problem within a Mozilla product or whether the problem lies somewhere else.
* Search for bugs already [https://bugzilla.mozilla.org/buglist.cgi?keywords=testcase-wanted%2C%20&keywords_type=allwords&f1=OP&list_id=6456823&f0=OP&o2=substring&f4=CP&query_format=advanced&j1=OR&f3=CP&f2=component&bug_status=UNCONFIRMED&component=Layout&v2=layout&product=Core tagged testcase-wanted] and try to develop a testcase.
*

Latest revision as of 19:24, 15 August 2013

Redirect to:

Retrieved from "https://wiki.mozilla.org/index.php?title=Bugmasters/Projects&oldid=695194"