VirtualBox

Changes between Version 67 and Version 68 of Bugtracker


Ignore:
Timestamp:
Feb 8, 2013 5:03:32 PM (11 years ago)
Author:
Michael Thayer
Comment:

More bug-tracker advice updates.

Legend:

Unmodified
Added
Removed
Modified
  • Bugtracker

    v67 v68  
    11= Bugtracker =
    22
    3 This site offers a public bugtracker. In case you encounter problems with !VirtualBox or have other suggestions for improvements, please use this facility to report those issues, which will then be called a "ticket". Each such ticket receives a unique number that you can later refer to in order to see if any progress was made, or add comments to it. 
     3This site offers a public bugtracker. In case you encounter problems with !VirtualBox or have other suggestions for improvements, you can use this facility to report those issues, which will then be called a "ticket". Each such ticket receives a unique number that you can later refer to in order to see if any progress was made, or add comments to it. 
    44
    55'''Please keep the following in mind before creating new tickets:'''
     6 * Before reporting a problem you are having as a bug in !VirtualBox, please do some research using search engines, in our [http://forums.virtualbox.org forums] and using the search engine on this page to see if other people know about the problem and have solutions.  Please also take the problem to the forums before creating a ticket and provide a link to the discussion (but still put all relevant information in the ticket).  And before adding comments to a ticket please go to the linked forum topic if any to work out if your issue is the same one.  See also [http://www.catb.org/~esr/faqs/smart-questions.html this guide to asking questions on-line].
    67 * We receive many more bug reports than we have time to look at properly (or even at all!), and we have to choose which ones we spend time on.  You can increase the chances that we look at your bug report by putting in the right work, both while and after reporting it (see for example [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html this guide to reporting bugs]).  However, please do not be offended if we are still unable to spend time on your report because we are forced to choose between it and other issues that appear more important to us.
    7  * If you are not sure whether or not the issue you have found is a bug in !VirtualBox, you might want to discuss it on the [wiki:"Mailing_lists" mailing lists] or the [http://forums.virtualbox.org VirtualBox forum].  See also [http://www.catb.org/~esr/faqs/smart-questions.html this guide to asking questions on-line].
    8  * Use the search function to find identical bugs others have opened before and report there instead of creating duplicate tickets.  If you add a comment to an existing ticket, you will receive e-mail notification every time that ticket is updated.
    9  * Try to clearly describe the bug and ways to reproduce it. '''Attach your !VirtualBox VM session log file (VBox.log) to the ticket! ''' This file includes a lot of useful information and saves us time asking you for it.  If you are using the main !VirtualBox user interface you can access the log files using the "Show Log..." entry in the "Machine" menu.
    10  * Please try to stay polite, respectful and relevant.  Abusive, offensive and aggressive comments will be deleted, as will off-topic comments if they make it hard to follow the issue under discussion in a bug ticket.
     8 * If you add a comment to an existing ticket, you will receive e-mail notification every time that ticket is updated.
     9 * If you cannot find a ticket describing your problem and create a new one, '''please attach your !VirtualBox virtual machine session log file (VBox.log) to the ticket! ''' This file includes a lot of useful information and saves us time asking you for it.  If you are using the main !VirtualBox user interface you can access the log files using the "Show Log..." entry in the "Machine" menu.
     10 * Please try to stay polite, respectful and relevant.  Abusive, offensive and aggressive comments will be deleted, as will off-topic comments if they make it hard to follow the issue under discussion in a bug ticket.  Unpleasant and uninformative ticket content not only reduces our desire to work on your ticket but also takes away time (and motivation!) that could be spent on other people's tickets.
    1111
    1212'''Note:''' To create new tickets, you must have registered with this site ''and''

© 2023 Oracle
ContactPrivacy policyTerms of Use