Talk:QA:Bugzilla:FAQ

Bugzilla FAQ revision items

• Revisions to the Bugzilla FAQ
  • QA:Bugzilla:Searching_For_Dupes
  • Instructions for tasks QA commonly asks reporters to do
    • Fresh profile
    • Move UA spoofing instructions here, from hidden prefs

    (Essentially, cb.o support needs a Camino version of this)

    • CUPS debug log (rare)
    • Console.log (rare)
  • "pay attention to your bug; we will ask you questions"
  • no private emails
  • new "Before filing bug" section
    • no UA spoofing
    • use latest version/nightly from last 2 weeks
    • Fresh profile
    • Check in Fx
    • QA:Bugzilla:Searching_For_Dupes
    • plus the crash/sample stuff there
    • Link to bug-reporting guidelines ??
  • When reporting a bug (beef up existing instructions)
    • File using the build in which you experienced the bug
    • no UA spoofing

      Some sample text here

    • Attach crash log or sample (already in the FAQ)
    • Screenshots in JPG or PNG, not PDF or TIFF
  • “Bugzilla is not a forum” - Behave! Link to https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
  • Bugzilla is not for support
• Put the Bugzilla FAQ in the Support sidebar (raise visibility in support vs in development)
  • Move some bug-reporting stuff from dev/ to sup/

Other thoughts

Note that the Bugzilla FAQ on cb.o will exist primarily for end-users (and for triage team members to point end-user to for instructions, etc.)

"Also, if you have debugging information that is more than 20 lines long, it should be an attachment rather than pasted into the Additional information." [1]

See also the AbiWord Bug FAQ; we should incorporate some of these items.

Samples of good initial bug reports: [2]

Getting a crash log manually

• Option B: the hard way (you've probably disabled CrashReporter)
  1. Open the Console application, located in the Utilities subfolder of the Applications folder.
  2. Click on the "Logs" toolbar icon if the logs drawer isn't showing on the left.
  3. In the list of logs on the left, select "~/Library/Logs" then "CrashReporter" then "Camino"
  4. Locate the appropriate log entry for the most recent crash. It should be the one at the bottom. Each individual crash log entry is separated by a line of asterisks from the next one above it; each entry has a date at the top of it.
  5. Select the entry, from the "Host name" down to the end of the entry and paste into a new plain-text document (in the TextEdit application, create a new document and choose Make Plain Text from the Format menu).

     N.B. The format of the crashlog varies between major Mac OS X versions.

  6. Attach this crashlog to the bug you filed.