Bugmasters/Projects/Nightly: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
m (→‎Nightly build bug team: changed email to tutorial link.)
 
(32 intermediate revisions by 2 users not shown)
Line 1: Line 1:
==Nightly build bug team==
==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]!
Hello! If you'd like to help out with bug management for Nightly builds, please read this page and try out the tutorial at http://www.tizianasellitto.it/trainingmontage/bugzilla-triage-tutorial.html.  


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]]).  
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]]).  
Line 8: Line 8:
  1. Download the Nightly build and run it.<br>
  1. Download the Nightly build and run it.<br>
  2. Make a bugzilla account.<br>
  2. Make a bugzilla account.<br>
  3. Skim over the [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=DUPLICATE&query_format=advanced&version=28%20Branch&product=Firefox&list_id=6602828 current bugs against the Nightly release] (currently, 28 build).<br>
  3. Skim over the [https://bugzilla.mozilla.org/buglist.cgi?list_id=9325172&resolution=---&resolution=DUPLICATE&query_format=advanced&version={{NIGHTLY VERSION}}%20Branch&product=Core&product=Firefox&product=Toolkit current bugs against the Nightly release] (currently, {{NIGHTLY VERSION}} branch).<br>  
  4. File bugs when you find them.<br>
  4. Triage through the list of [https://bugzilla.mozilla.org/buglist.cgi?list_id=9636938&resolution=---&resolution=DUPLICATE&query_format=advanced&bug_status=UNCONFIRMED&version={{NIGHTLY VERSION}}%20Branch&version={{NIGHTLY VERSION}}%20Branch&product=Core&product=Firefox&product=Toolkit UNCONFIRMED Nightly bugs]. So helpful!<br>
5. Triage through the list of Nightly bugs. So helpful!<br>
  --- replicate the bug, comment, and confirm it<br>
  --- replicate the bug, comment, and confirm it<br>
  --- needinfo the bug reporter to get more details<br>
  --- needinfo the bug reporter to get more details<br>
Line 16: Line 15:
<br>
<br>


For example, the current released version of Firefox is 25.0. The [http://www.mozilla.org/en-US/firefox/channel/ Beta] version is 26, and the Aurora version is 27. That means the Nightly build is 28. The bugs filed against that release are listed as being in the [https://bugzilla.mozilla.org/buglist.cgi?resolution=---&resolution=DUPLICATE&query_format=advanced&version=28%20Branch&product=Firefox&list_id=6602828 28 branch] of Firefox.
For example, the current release version of Firefox is {{RELEASE VERSION}}. The [http://www.mozilla.org/en-US/firefox/channel/ Beta] version is {{BETA VERSION}}, and the Aurora version is {{AURORA VERSION}}. That means the Nightly build is {{NIGHTLY VERSION}}. The bugs filed against that release are listed as being in the [https://bugzilla.mozilla.org/buglist.cgi?list_id=9325172&resolution=---&resolution=DUPLICATE&query_format=advanced&version={{NIGHTLY VERSION}}%20Branch&product=Core&product=Firefox&product=Toolkit {{NIGHTLY VERSION}} branch] of Firefox.
 
==UNCONFIRMED bugs in the {{NIGHTLY VERSION}} Branch (Nightly)==
 
{{ForceRefreshButton}}


<onlyinclude>
<onlyinclude>
Line 24: Line 27:
     "include_fields": "id, summary, product, component, status, op_sys",
     "include_fields": "id, summary, product, component, status, op_sys",
     "order": "bug_id",
     "order": "bug_id",
    "product": ["Firefox", "Core", "Toolkit"],
     "status": "UNCONFIRMED",
     "status": "UNCONFIRMED",
      "version": "28 Branch"
    "version": "{{NIGHTLY VERSION}} Branch"


}
}
</bugzilla>
</bugzilla>
</onlyinclude>
</onlyinclude>
Note:
* Bugs that [https://bugzilla.mozilla.org/buglist.cgi?list_id=9380693&resolution=---&resolution=DUPLICATE&chfieldto=Now&chfield=bug_status&query_format=advanced&chfieldfrom=2013-01-01&chfieldvalue=NEW&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&version={{NIGHTLY VERSION}}%20Branch&version={{NIGHTLY VERSION}}%20Branch&product=Core&product=Firefox&product=Toolkit changed state from UNCO to NEW].  (Active triaging happened to move them to NEW)
* Total number of bugs reported for {{NIGHTLY VERSION}} Branch that were [https://bugzilla.mozilla.org/buglist.cgi?list_id=9380304&resolution=---&resolution=DUPLICATE&query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&version={{NIGHTLY VERSION}}%20Branch&product=Core&product=Firefox&product=Toolkit confirmed] (Including bugs that were originally filed as NEW)
==Firefox Untriaged bugs in {{NIGHTLY VERSION}} Branch==
Bugs that are in the Firefox Untriaged component, reported for {{NIGHTLY VERSION}} branch.  The UNCONFIRMED bugs need to be replicated and their status changed to NEW. Often they turn out to be support issues. In that case mark them as RESOLVED INVALID and redirect the person who filed the bug to Support.
<onlyinclude>
<bugzilla>
{   
    "include_fields": "id, summary, product, component, status, op_sys",
    "order": "bug_id",
    "product": "Firefox",
    "component": "Untriaged",
    "status": "UNCONFIRMED",
    "version": "{{NIGHTLY VERSION}} Branch"
}
</bugzilla>
</onlyinclude>
The following bugs have been replicated, or confirmed as NEW, but haven't yet been assigned to a product and component. It's important to make an effort to get these bugs into a category where developers on particular teams are more likely to see them.
<onlyinclude>
<bugzilla>
    "include_fields": "id, summary, product, component, status, op_sys",
    "order": "bug_id",
    "product": "Firefox",
    "component": "Untriaged",
    "status": "NEW",
    "version": "{{NIGHTLY VERSION}} Branch"
}
</bugzilla>
</onlyinclude>


* 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.
* 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.
Line 37: Line 76:
** https://blog.mozilla.org/channels/2011/07/18/every-six-weeks/
** https://blog.mozilla.org/channels/2011/07/18/every-six-weeks/


Other ways to help with the Nightly release: [https://wiki.mozilla.org/Releases/Firefox_28/Test_Plan QA Test Plan for Firefox 28]
Other ways to help with the Nightly release: [https://wiki.mozilla.org/Releases/Firefox_{{NIGHTLY VERSION}}/Test_Plan QA Test Plan for Firefox {{NIGHTLY VERSION}}]

Latest revision as of 19:33, 25 June 2015

Nightly build bug team

Hello! If you'd like to help out with bug management for Nightly builds, please read this page and try out the tutorial at http://www.tizianasellitto.it/trainingmontage/bugzilla-triage-tutorial.html.

Every night the latest pre-release version of Firefox is made available. If you want to test against the cutting edge of Firefox, 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.
2. Make a bugzilla account.
3. Skim over the current bugs against the Nightly release (currently, 146 branch).
4. Triage through the list of UNCONFIRMED Nightly bugs. So helpful!
--- replicate the bug, comment, and confirm it
--- needinfo the bug reporter to get more details
--- regression testing with the mozregression tool


For example, the current release version of Firefox is 144. The Beta version is 145, and the Aurora version is 54. That means the Nightly build is 146. The bugs filed against that release are listed as being in the 146 branch of Firefox.

UNCONFIRMED bugs in the 146 Branch (Nightly)


No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);



Note:

  • Bugs that changed state from UNCO to NEW. (Active triaging happened to move them to NEW)
  • Total number of bugs reported for 146 Branch that were confirmed (Including bugs that were originally filed as NEW)

Firefox Untriaged bugs in 146 Branch

Bugs that are in the Firefox Untriaged component, reported for 146 branch. The UNCONFIRMED bugs need to be replicated and their status changed to NEW. Often they turn out to be support issues. In that case mark them as RESOLVED INVALID and redirect the person who filed the bug to Support.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);


The following bugs have been replicated, or confirmed as NEW, but haven't yet been assigned to a product and component. It's important to make an effort to get these bugs into a category where developers on particular teams are more likely to see them.

No results.

0 Total; 0 Open (0%); 0 Resolved (0%); 0 Verified (0%);



  • To search later branches, go to the 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.

Other ways to help with the Nightly release: QA Test Plan for Firefox 146