Confirmed users
538
edits
SeaMonkey/Bugzilla-FAQ: Difference between revisions
→Whiteboard: Good first bug
m (Rrbd moved page SeaMonkey/Mozilla-FAQ to SeaMonkey/Bugzilla-FAQ: Wrong Name) |
(→Whiteboard: Good first bug) |
||
| (30 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Here you find suggestions how to | {{SeaMonkey-Resources}} | ||
Here you find suggestions how to use '''''Bugzilla''''' for several questions without an answer in ''Mozilla'' [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Bug writing guidelines]. | |||
== Before you start == | |||
;What issues are worth to be reported at Bugzilla? | |||
: Anything wrong (or needing improvement) what can't be fixed immediately by user who observed the problem. Don't be shy, but consider that every report should be created with care according to ''[https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines Mozilla Bug writing Guidelines]'' | |||
== General == | |||
=== How to unsubscribe from Bugzilla === | |||
Mostly the goal is to stop receipt of automated Bugzilla Messages. Users can do that without help: | |||
# Open any Bugzilla page in your browser (by clicking on Bugzilla hyperlink in an e-mail you got from Bugzilla system) | |||
# log in | |||
# in heading area (Home - New - ...) click ''Preferences'' | |||
# on Preferences page click ''Email Preferences' (location of this hypelink might depend on selected ''Skin'' for Bugzilla User Interface | |||
# Click button ''Disable all Bugmail'' | |||
# Click button ''Save Changes'' | |||
'''Ready!''' | |||
: Additional help you can find in [https://bugzilla.readthedocs.org/en/5.0/using/preferences.html#email-preferences Bugzilla Documentation] | |||
:If you can no longer login because you forgot your user data, you may ask a Bugzilla expert from [[SeaMonkey/Supporters]]. | |||
If you want to unsubscribe ''completely'' from Bugzilla you will need an administrator's help via [[SeaMonkey/Supporters]] | |||
---- | |||
== Bug Report Details == | |||
=== How to read User Agent string information === | |||
Menu 'Help → about SeaMonkey' shows something like <br /> | |||
: '''<big>User-Agent: <span style="color:#800080"> Mozilla/5.0 </span> ( <span style="color:#008000"> Windows NT 6.1 </span>; <span style="color:#808000"> WOW64 </span> ; <span style="color:#000080">rv:41.0 </span> ) <span style="color:#008080"> Gecko/20100101 </span> <span style="color:#c0c0c0"> Firefox/41.0 </span> <span style="color:#ff0000"> SeaMonkey/2.38 </span> <span style="color:#ff00ff"> Build identifier: 20150923195647 </span></big> '''<br /> | |||
You can find some explication on [https://developer.mozilla.org/en-US/docs/Web/HTTP/Gecko_user_agent_string_reference MDN], [https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/ hacks.mozilla.org] and [http://www.useragentstring.com/ useragentstring.com] (will analyze your user agent string). | |||
: | |||
Some more details: | |||
* <span style="color:#800080"> '''Mozilla/5.0''' </span>: Mozilla token <!-- What ever 5-0 might mean --> | |||
* <span style="color:#008000"> '''Windows NT 6.1''' </span> : Platform identifier shows on what operating system that SeaMonkey version is used. | |||
** Windows explained at [https://en.wikipedia.org/wiki/Windows_NT#Releases Wikipedia] | |||
* <span style="color:#808000"> '''WOW64''' </span> : operating system and SeaMonkey details: | |||
** [https://de.wikipedia.org/wiki/WOW64 WOW64]: 32 bit SeaMonkey [https://en.wikipedia.org/wiki/Software_build build] on [https://en.wikipedia.org/wiki/64-bit_computing 64 bit] Windows | |||
** [https://en.wikipedia.org/wiki/X86-64 x64]: 64 bit SeaMonkey build on 64 bit Windows | |||
*<span style="color:#000080">'''rv:41.0 '''</span>: [https://en.wikipedia.org/wiki/Gecko_%28software%29 Gecko] [https://en.wikipedia.org/wiki/Web_browser_engine rendering engine] version | |||
* <span style="color:#008080"> '''Gecko/20100101''' </span> : used to indicate the build date, but was considered a major source for browser fingerprinting; replaced by a constant dummy date since, it was retained for compatibility reasons. | |||
* <span style="color:#c0c0c0"> '''Firefox/41.0''' </span> : Firefox version what is basis of this SeaMonkey (browser) version | |||
* <span style="color:#ff0000"> '''SeaMonkey/2.38''' </span> : SeaMonkey version | |||
* <span style="color:#ff00ff"> '''Build identifier:''' 20150923195647 </span> : Unique timestamp of the build, not exposed in the user-agent string | |||
---- | |||
== How to use attached sample documents for multiple Bug Reports == | == How to use attached sample documents for multiple Bug Reports == | ||
| Line 6: | Line 51: | ||
The advantage compared to a copy is that everybody knows that the sample document in the new document is identical (the same) as in the other bug where the attachment has been added; so it is much more easy to compare results. | The advantage compared to a copy is that everybody knows that the sample document in the new document is identical (the same) as in the other bug where the attachment has been added; so it is much more easy to compare results. | ||
---- | |||
== Bugzilla fields == | |||
=== Version === | |||
Should show the earliest (''SeaMonkey'') version with the reported problem. Together with ''Target Milestone'', this field marks the range of (SeaMonkey) versions with the reported problem. This range-information is important for several useful Bugzilla-Queries, for example | |||
* Decision whether an observed problem already has been reported. | |||
:If a bug report is concerning a problem with similar symptoms, but ''Version'' or ''Target Milestone'' do not match, the observed problem can not have the same roots as the problem of the other bug report. Example: You observe that in Browser background pictures are not shown and you find a possible DUPlicate in a Bugzilla, you should compare ''Version'' and ''Target Milestone'' of that Bug with your observations. If the problem you observe started with the same SeaMonkey version as indicated in that Bug report, but that problem has become fixed for a SeaMonkey 2 Versions before yours, your observations are concerning a different problem, or the Fix for the other Bug is incomplete concerning the aspect causing the problem you observe. | |||
=== Target Milestone=== | |||
* For ''RESOLVED - FIXED'': should show the earliest ''SeaMonkey'' version for what the bug has been fixed (known fix). Target information can be used in queries much more effected than the ''Status Flag'' "fixed" to find out with what version a particular problem became solved by a fix. | |||
* For ''RESOLVED - WORKSFORME'' or similar resolution: Shows the earliest ''SeaMonkey'' version behind ''Version'' for what the bug now longer is reproducible (fix unknown) | |||
Together with ''Version'', ''Target Milestone'' marks the Range of (SeaMonkey) versions with the reported problem. This range-information is important for several useful Bugzilla-Queries, for example | |||
* Decision whether you should update to a later version or whether that version contains regressions which are fatal for you. | |||
: This [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=SM2.47PossibleRegressions&sharer_id=41036&list_id=13327785 example] (Bugzilla account required) shows a query for the decision "should I update from SeaMonkey 2.40 to 2.47?". It lists problems (some still UNCONFIRMED) which appeared after ''Version'' '''2.40''', but still have not become FIXED for ''Target Miestone'' '''2.47'''. | |||
=== Resolution === | |||
; ''DUPLICATE'' or ''INVALID'' for accidentally created clones? | |||
: Sometimes a bug report ends up in the Bugzilla database twice in a row. If you see two bugs with the same summary and adjacent bug numbers, mark one as '''''INVALID'''''. ''DUPLICATE''s are indication that the problem affects many users or appears in different components (or may be the bug description is not optimum). The DUPLICATEs, what might contain important additional information, will have to be included into the Bug proceeding process, and especially when a fix is available it should be tested for all aspects mentioned in the DUPLICATEs. An accidentally created ''clone'' simply is '''INVALID''' and worthless for the bug fixing process. To avoid unnecessary interest for that clone, don't mention it in "See Also" of the remaining Bug report (or anywhere else), only leave a comment in the clone referring to the remaining Bug Report like "Accidentally created clone of Bug 123456". | |||
== Whiteboard == | |||
Should be used for search strings suitable for ''Bugzilla'' queries. That means ''Whiteboard'' entries should "tag" common characteristics of Bugs with the same Whiteboard entries. For important bug report internal ints (Workaround: see comment 17) pleas use field "User Story" | |||
=== SeaMonkey internal Whiteboard tags === | |||
Please only use for Products with ''SeaMonkey'' in it's name andcopy/paste the tag from here to whiteboard field. | |||
;[easyconfirm] | |||
: for Bugs suitable for [[SeaMonkey/QA|QA]] beginners. Report has a good step by step instruction how to reproduce, but still additional information will be required. | |||
;[good first bug] | |||
: for Bugs suitable for [[SeaMonkey/Supporters|new developers]]. Report has a good step by step instruction how to reproduce, and it seems that the bug can be fixed easily if the volunteers has skills in the required area. | |||
== QA Whiteboard == | |||
To be continued | |||