Bug Reporting Guidelines

[Jan]

EDIT: WINDOWS 7 USERS: PLEASE DO NOT POST BUG REPORTS, WIN7 IS NOT OFFICIALLY SUPPORTED YET. PLEASE USE THE SUPPORT REQUEST FORUM FOR ANY ISSUES YOU MAY EXPERIENCE.

1. User MUST post a system report. Bug reports without a system report will be deemed as not a bug. Developers spending time trying to track down system reports could be better spending their time developing.

   To post a system report:
   

   1. Enable all system logs (enable "Log Events" in General, Phone, and SatRadio settings, these are all off by default in 2.0 RC7+). Or, pass "-logevents" command line parameter to enable all logs.
   2. Close CF (not necessary but is helpful so we can see CF starting in the logged events)
   3. Restart CF.
   4. Reproduce issue, and don't do anything else thereafter except #5 below.
   5. Go into Settings, select "Generate System Report", which will generate a .flux file and save it to your desired location.
   6. Post the .flux/.zip file with your described issue.

   In your bug report, please describe what the log will show us. For example, "Started CF, entered media screen, loaded 4 playlists from library, ejected a playlist, album art does not show properly, created report, exited CF".
   

2. User MUST be running the latest release of Centrafuse. All bug reports from anything but the latest release of Centrafuse will be ignored. The version of the software that is currently running on the system is documented in the System report. The developers will be checking this before digging into a report. Code changes and fixes are implemented. If you're not running the latest release and are experiencing issues, please update The time a developer spends tracking down a bug that could possibly be fixed in the most recent release could be better spent writing code to fix current issues or adding new functionality.
3. User MUST NOT be running any 3rd party plug-ins at the time of a bug report and system report generation. This information shows up in the system report and will be checked. A simple solution has been placed into effect for 2.0 RC7 in order to make it quick and easy to disable 3rd party plug-ins. Please utilize this solution before posting a bug report. If you disable plug-ins and the issue is no longer present, then it's a 3rd party plug-in issue, plain and simple. Please report the bug to the developer of the 3rd party plug-in as it is not the responsibility of Centrafuse to support these plug-ins. Time spent tracking down issues related to these plug-ins is time that a developer could have spent fixing current known bugs or implementing new features. Just pass the “-disable3rdplugins” parameter as outlined here (option #2). If the issue still persists, then please post your system report accordingly.
   
4. Bug reports without a requested response by the development and support teams will be closed after 72 hours. If a user doesn't haven't he time to follow-up on a bug report, then there's just not much we can do to try and solve the problem. Again, the time a developer has to spend to ask for updates is time that the developer could be spending actually developing.