User:Tyler/BMOsurvival3: Difference between revisions

Jump to navigation Jump to search
text now
(New page: This page will come together)
 
(text now)
Line 1: Line 1:
This page will come together
<h1>BMO Survival Guide</h1>
<h2>PART 3 </h2>
<h1>Advanced BMO Details and FAQs </h1>
<p>While the first two parts of this guide give you the basics you need to survive on BMO, and how bug's work. However, there is so much more to BMO, most of which can not be covered without writing a very thick book, which would be out of date before it was printed. This last part of the guide will cover some of the more advanced details on BMO, and a bunch of Misc things to cover. </p>
 
<h2>Patches</h2>
<h2>Teams</h2>
<h2>FIXED, RESOLVED, VERFIED, WHAT? </h2>
<p>When the bugzilla product was written, the developers placed two levels or closing a bug. the first is Resolved whatever (DUPLICATE, FIXED, etc.). Beyond that, after a bug is resolved, it can be Verified as whatever it was resolved as. The main advantage of this approach is that it gives a second opinion, and ideally, in a perfect world, every bug should end as being verified. Unfortunately, this is not a perfect world. the majority of bugs are resolved, and that is as far as they get. There are simply too many bugs, and too few triage members. Only a portion of resolved bus will be verified. So, the usual approach is this: while verified is nice, we have to live with resolved. Of course, if you enjoy making sure resolutions are accurate, by all means verify bugs. </p>
<h2>Testing Bugzilla, the Product </h2>
<p>We understand if you want to play around and test the actual Bugzilla product (<a href="http://www.bugzilla.org">www.bugzilla.org</a>). However, BMO is not the correct place to do that. You should use <a href="http://landfill.mozilla.org" target="_blank">landfill.bugzilla.org</a> </p>
<h2>The Whiteboard, Again</h2>
 
<p>We already went over the whiteboard, right? Wrong. The whiteboard is one of the most misunderstood and confusing aspects of a bug, even for developers. So, even the things said in this section could be in turmoil right now. </p>
<p>The whiteboard is a place where notes can be placed on a bug, keywords that are not keywords, or a request that something be done (such as a review).</p>
<p>One popular whiteboard note is CLOSEME. This note is supposed to be placed on the whiteboard of a bug that has not had any activity after a period of time (usually 3 weeks). The person who places the note should also place  a comment asking for the required information. The close will have a date on it. One that date, the bug is supposed to be closed as INCOMPLETE, WFM, whatever resolution is appropriate. In theory, every bug that has had no comment after a request for more information should have this note added, and then be closed at the date specified. As already noted, theory does not always play out in the real world. So, while it would be nice to have a very orderly way of closing abandoned bugs, CLOSEME is not universally used, nor is it required to close a bug. </p>
<h2>Handy Hints and Tricks </h2>
<h2>Privileges</h2>
<p>When you first sign up with BMO, you will be able to do very little. you can file a bug, and make changes to most areas of your won bug, and you can add comments and attachments to other bugs. However, you can not change the status or product, or change any fields of someone else's bug. You will need to be able to get extended privileges to do that.</p>
<p>Canconfirm: With these privileges, you can confirm any bug.<br />
Canedit: With these privileges, you can edit any area of any bug. </p>
<p>These are about the highest privs that most members of the community will get. Module owners, and Mozilla employees will be given more privileges as required.</p>
 
<p>Now, how do you get privileges? You need to demonstrate that you deserve them.  </p>
<h2>FAQs</h2>
<h2>A List of Resources </h2>
<h2>[https://wiki.mozilla.org/User:Tyler/BMOsurvival2&lt;&lt;&lt; Previous Page - Bug Reports, from Top to Bottom]</h2>
Confirmed users
494

edits

Navigation menu