http://www.mozilla.org/quality/bug-writing-guidelines.html
Are you in the right place?
Are reports from Netscape users still a problem? If not, can we remove this? We should get into the meat quicker.
The Mozilla bug tracking system (Bugzilla) allows any interested individuals on the Internet to directly report and track bugs in mozilla.org open-source projects like the Mozilla Application Suite or Mozilla Firebird.
Our issue tracking system (Bugzilla) allows any interested individual to report and track issues in mozilla.org products like the Mozilla Application Suite or Mozilla Firebird.
Like you, Mozilla QA (Quality Assurance) wants your bug reports to result in bug fixes; the more effectively a bug is reported, the more likely that an engineer will actually fix it.
mozilla.org QAs (Quality Assurance) want your bug reports to result in bug fixes; the clearer and more useful a bug report is, the more likely that an engineer will fix it.
By following these guidelines, you can help ensure that your bugs stay at the top of the Mozilla engineers' heap, and get fixed.
By following these guidelines, you can help ensure that your reports recieve the proper attention and get resolved.
Bugzilla is the preferred method of submitting a bug - the linked entry form incorporates parts of these guidelines.
"the linked entry form" is probably confusing except to the document writer. Remove this sentence. Also, the first sentence should probably be merged to the previous paragraph: "...the more likely that an engineer will actually fix it. By following these guidelines, you can help ensure that..."
If an engineer can't see it or conclusively prove that it exists,
If an engineer cannot conclusively prove that it exists,
the engineer will probably stamp it "WORKSFORME" or "INVAliD", and
move on to the next bug.
INVALID "and moves on..."
If you're crashing on a site, please take the time to isolate what on the page is triggering the crash, and include it as an HTML snippet in the bug report if possible.
If you crash on a site, take the time to isolate what on the page is triggering the crash, and include it as an HTML snippet in the bug report if possible.
(Specific bugs have the added bonus of remaining relevant when an engineer actually gets to them; in a rapidly changing web, a bug report of "foo.com crashes my browser" becomes meaningless after the site experiences a half-dozen redesigns and hundreds of content changes.)
remove the brackets.
"specific bugs" sounds like "certain bugs".
Explicit bugs have the benefit of remaing relevant. In a rapidly changing Web, ... browser" may become meaningless after the site experience re-design or content changes.
Let's say you crash at foo.com, and want to write up a bug report:
Let's say you crash at foo.com and want to file a bug report:
Mozilla crashed each time upon drawing the Foo banner at the top of the page.
nees a "Good:" label
If your problem is Mozilla crashing, Talkback data is very helpful in diagnosing the problem.
If your problem is Mozilla crashing, Talkback data is very helpful for engineers diagnosing the problem.
If you can consistently reproduce the crash, please download
a build with Talkback and install it.
If you can consistently reproduce the crash, download and install a build with Talkback.
Then, do what is necessary to reproduce the crash, and follow
the instructions for sending crash data to the server.
Then, reproduce the crash and follow the on-screen instruction for sending crash data to the server
Lastly, run the program components/talkback.exe (Win32)
(Windows)
Before you enter your bug, you need to make sure it has not been previously reported. There is a tutorial on the best ways of doing this.
A large number of bug reports are duplcates of previously reported ones. Before filing a bug report, make sure it has not been reported. There is a tutorial on the best ways of doing this.
Next, be sure that you've reproduced your bug using a build released within the past three days. Our development process moves at lightning speed, and the bug you've found may already have been fixed. (Nightly builds can be downloaded from the mozilla.org binaries page.)
Be sure that you can reproduce your bug in a <a href="http://www.mozilla.org/developer/#builds";>nightly build</a> released within the past three days. Our development process moves at lightning speed, and the bug may already have been fixed.
Is "three days" too much? This guidelines is more for new bug reporters who tend to be less enthusiastic than most QAs. The time period should be in line with the start/ page (two week?)
If you've discovered a new bug using a current build, report it in the guided Bugzilla entry form.
Remove. People without canconfirm previlege don't know there is an "unguided version". And those who should use the guided form have to use it anyway.
You just filled this out on the last page.
in the previous page
Version: In which product version did you find the bug? We're not yet using this field. Just leave the default value as you found it. ;)
is this still true? and loose the smily
(If they all look meaningless, click on the Component link, which links to descriptions of each component, to help you make the best choice.)
Component link should link to http://bugzilla.mozilla.org/describecomponents.cgi
click on the Severity link
link to http://bugzilla.mozilla.org/queryhelp.cgi#severity
> ... submitting a bug report; the text box exists to allow you to
manually assign it to a different engineer.
...submitting a bug report. The text box allows you to
If you encountered the bug on a particular URL, please provide it (or, them) here.
I don't think it's good practice to file a bug report against several URLs. If the bug exists in many URLs, the reporter should find the one that best represents the issue and stick it in the URL field. I'll go with just "it"
Also, "on a particular Web location"
Summary: How would you describe the bug, in approximately 60 or fewer characters?
in 10 to 15 words or less
Otherwise, developers cannot meaningfully query by bug summary,
what does "query" mean? replace with "search" I'm not sure about "meaningfully". fantasai, suggestion?
Please provide as detailed of a problem diagnosis in this field as possible, including as much as possible of the following information:
Please provide a detailed problem diagnosis, including...
Overview Description: More detailed expansion of summary.
"Overview" is enough
Drag-selecting any page crashes Mac OS X builds in NSGetFactory
use the .example class
_______________________________________________ mozilla-documentation mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-documentation
