From 4bbb07e8048ef859cfc29c6b9d221840f2c6aed1 Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Fri, 16 Jan 2004 06:34:12 +0000 Subject: Phase 1 of a big documentation update before 2.17.6. --- docs/html/bugreports.html | 197 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 197 insertions(+) create mode 100644 docs/html/bugreports.html (limited to 'docs/html/bugreports.html') diff --git a/docs/html/bugreports.html b/docs/html/bugreports.html new file mode 100644 index 000000000..91df7f3ba --- /dev/null +++ b/docs/html/bugreports.html @@ -0,0 +1,197 @@ +
Years of bug writing experience has been distilled for your + reading pleasure into the + Bug Writing Guidelines. + While some of the advice is Mozilla-specific, the basic principles of + reporting Reproducible, Specific bugs, isolating the Product you are + using, the Version of the Product, the Component which failed, the + Hardware Platform, and Operating System you were using at the time of + the failure go a long way toward ensuring accurate, responsible fixes + for the bug that bit you.
The procedure for filing a test bug is as follows:
Go to + Landfill + in your browser and click + Enter a new bug report. +
Select a product - any one will do.
Fill in the fields. Bugzilla should have made reasonable + guesses, based upon your browser, for the "Platform" and "OS" + drop-down boxes. If they are wrong, change them.
Select "Commit" and send in your bug report.