|
|
Bugzilla Guide
From NeoWiki
(Difference between revisions)
| Revision as of 09:27, 17 March 2005 (edit) Sardisson (Talk | contribs) (brazenly steal ed's explanation of getting a crashlog) ← Previous diff |
Revision as of 05:34, 5 April 2005 (edit) (undo) Sardisson (Talk | contribs) (links to Oscar's newest finds) Next diff → |
||
| Line 1: | Line 1: | ||
| == Things to Do == | == Things to Do == | ||
| - | + | # New front page (bypassable for certain users, i.e. admins or long-time good bugfilers) or something like [https://bugzilla.mozilla.org/enter_bug.cgi?product=Camino&format=guided Bugzilla Helper] | |
| - | + | #* Steps to take before filing a bug | |
| - | + | #** Install latest patch [link] | |
| - | + | #** Reboot | |
| - | + | #** Fresh profile | |
| - | + | #** Attempt to reproduce in corresponding version of OOo/X11 if possible (?) | |
| - | + | #** Search for duplicate | |
| - | + | #* Scope of bugs, i.e. what's a Neo/J bug vs. an OOo bug/limitation vs. an Apple bug/limitation | |
| - | + | #* How to submit a useful bug report | |
| - | + | # Write "How to submit a useful bug report" | |
| - | + | #* One issue per bug report | |
| - | + | #* Include Patch level and OS version | |
| - | + | #* How to get a crashlog to attach | |
| - | + | #** Option A: is crashreporter enabled? Copy/paste into new text file. | |
| - | + | #** Option B: the hard way | |
| - | + | #***Open Applications > Utilities > Console | |
| - | + | #***Click on the "Logs" toolbar icon if the logs drawer isn't showing on the left. | |
| - | + | #***Navigate through the list until you get to ~/Library/Logs > CrashReporter > soffice.bin.crash.log | |
| - | + | #***Locate the appropriate log for the most recent/remembered crash. It should be the one at the bottom. Each individual crash log is separated by a line of asterisks from the next one above it; each one has a date at the top of it. | |
| - | + | #***Copy from the "Host name" down to the end. Edit > Copy. Places a copy of the log onto the Clipboard | |
| - | + | #***Open TextEdit and create a new plain-text file. Paste the crashlog. (Hmm, isn't there an "export" function in Console.app that will grab the last log entry?) | |
| - | + | #* Attach (not paste) crashlog | |
| - | + | #** After bug is filed | |
| - | + | #** Add attachments separately from comments (attachment refresh wipes comments, currently no warning) | |
| - | + | #* Attach screenshot if relevant | |
| - | + | #* Attach problematic document, if relevant, or email it to Patrick if sensitive | |
| - | + | #* Example of a pretty solid report: http://bugzilla.neooffice.org/bug.php?op=show&bugid=554 | |
| - | + | #* [[User:Ovvldc|Oscar]] provides two links to general "good bug-filing behavior" articles. We should be sure to include the highlights and perhaps link to them "for more details" or something: | |
| - | + | #** [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively] | |
| - | * Change Advanced Query to be the default search | + | #** [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way] (a much longer piece also dealing with general "getting support/answers" issues) |
| - | :Basic query is absolutely useless for finding duplicates! | + | # Change Advanced Query to be the default search |
| + | #:Basic query is absolutely useless for finding duplicates! | ||
Revision as of 05:34, 5 April 2005
Things to Do
- New front page (bypassable for certain users, i.e. admins or long-time good bugfilers) or something like Bugzilla Helper
- Steps to take before filing a bug
- Install latest patch [link]
- Reboot
- Fresh profile
- Attempt to reproduce in corresponding version of OOo/X11 if possible (?)
- Search for duplicate
- Scope of bugs, i.e. what's a Neo/J bug vs. an OOo bug/limitation vs. an Apple bug/limitation
- How to submit a useful bug report
- Steps to take before filing a bug
- Write "How to submit a useful bug report"
- One issue per bug report
- Include Patch level and OS version
- How to get a crashlog to attach
- Option A: is crashreporter enabled? Copy/paste into new text file.
- Option B: the hard way
- Open Applications > Utilities > Console
- Click on the "Logs" toolbar icon if the logs drawer isn't showing on the left.
- Navigate through the list until you get to ~/Library/Logs > CrashReporter > soffice.bin.crash.log
- Locate the appropriate log for the most recent/remembered crash. It should be the one at the bottom. Each individual crash log is separated by a line of asterisks from the next one above it; each one has a date at the top of it.
- Copy from the "Host name" down to the end. Edit > Copy. Places a copy of the log onto the Clipboard
- Open TextEdit and create a new plain-text file. Paste the crashlog. (Hmm, isn't there an "export" function in Console.app that will grab the last log entry?)
- Attach (not paste) crashlog
- After bug is filed
- Add attachments separately from comments (attachment refresh wipes comments, currently no warning)
- Attach screenshot if relevant
- Attach problematic document, if relevant, or email it to Patrick if sensitive
- Example of a pretty solid report: http://bugzilla.neooffice.org/bug.php?op=show&bugid=554
- Oscar provides two links to general "good bug-filing behavior" articles. We should be sure to include the highlights and perhaps link to them "for more details" or something:
- How to Report Bugs Effectively
- How To Ask Questions The Smart Way (a much longer piece also dealing with general "getting support/answers" issues)
- Change Advanced Query to be the default search
- Basic query is absolutely useless for finding duplicates!
