Changes between Version 96 and Version 97 of Bugtracker

Timestamp:

Nov 24, 2016 11:16:44 AM (7 years ago)

Author:

Michael Thayer

Comment:

Instructions for the new ticket page too.

Bugtracker

@@ -10 +10 @@
  * '''Do some research''' (e.g. using search engines, our [http://forums.virtualbox.org forums] and [search:?link&q=&ticket=on existing bug tickets]) before creating a ticket.  Try to '''solve as much of the problem''' as you can yourself or in collaboration with other users.
  * Describe as precisely as you can '''how to reproduce the problem''', bearing in mind that it may be triggered by something special on your own computer system.  Fixing problems which cannot be reproduced is long and painful, both for the developer '''and the bug reporter'''.  It may help to find other people with the same problem and compare notes.
- * '''Attach a log file.'''  The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run.
+ * '''Attach a (full) log file''' straight away to save time for you and for us.  The log file contains a lot of useful information about both the host and the guest systems as well as information about what happened during a particular machine run.  Please '''do not cut and paste it'''.
+ * Look for possible [https://www.virtualbox.org/search?q=&ticket=on duplicate tickets] and [https://forums.virtualbox.org/ end-user forum] topics first, but unless you are sure, create a new ticket and point out the possible duplicates there.
  * '''Choose a summary carefully.'''  The bug tracker and ticket notifications are mainly seen by (busy) developers, and unless a summary catches their eye and looks related to the things they as an individual work on the ticket may not even be read.
- * Please stay '''polite, relevant and on-topic'''.  Try to avoid creating tickets for issues which are already being worked on, but do also try to avoid commenting on a ticket if you are not sure that your problem is the same (and not just similar) - if the ticket contains a link to a forum topic, consider going there first.  Offensive or unrelated comments and tickets take time away from other things and sap our and other people's motivation; in extreme cases we can delete them.
+ * Please stay '''polite, relevant and on-topic'''.  Offensive or unrelated comments and tickets hurt everyone and may be deleted.
+ * Do '''not''' report compile and development problems here, use the [https://www.virtualbox.org/mailman/listinfo/vbox-dev developer mailing list] for such problems.
+ * If you want to report a '''crash''' of !VirtualBox on a Linux/Solaris host, please provide a [https://www.virtualbox.org/wiki/Core_dump core dump] if possible.  If you want to report a crash on a Windows host, please attach a [https://www.virtualbox.org/wiki/User_FAQ#Windowsminidumps minidump] if possible.
+ * Use `{{{` and `}}}` to enclose verbose text. See [https://www.virtualbox.org/wiki/WikiFormatting Wikiformatting] for more details on how to use other format specifiers to make your text look pretty.
 
-'''Note:''' To create new tickets, you must have registered with this site ''and''
+To create new tickets, you must have registered with this site ''and''
 be logged in with your user name and password. Use the "Register" and "Login" links at the top right for that.  If you add a comment to an existing ticket, you will receive e-mail notification every time that ticket is updated.