Difference between revisions of "Bug Tracking System"

From MythTV Official Wiki
Jump to: navigation, search
(Misc tidy-ups, include info on discussing bugs)
("Myth" != MythTV. Fix svn's. Update instructions.)
 
Line 1: Line 1:
Myth now uses [http://svn.mythtv.org/trac Trac], a popular bug-tracking system.  When submitting bugs, there are a few rules and suggestions you should follow.
+
MythTV now uses [http://code.mythtv.org/trac Trac], a popular bug-tracking system.  When submitting bugs, there are a few rules and suggestions you should follow.
  
* '''Read the [http://svn.mythtv.org/trac/wiki/TicketHowTo Ticket HowTo] and once done, read it again'''
+
* '''Read the [http://code.mythtv.org/trac/wiki/TicketHowTo Ticket HowTo] and once done, read it again'''
* Report bugs against the most recent SVN code, or failing that the latest release, and select the appropriate release when submitting your ticket.
+
* Report bugs against the most recent unstable/development code, or failing that the latest release, and select the appropriate version under "Version" when submitting your ticket.  Do not specify "Milestone", "Priority", or "Severity"--these will be filled out by the developers.
* Search the [http://svn.mythtv.org/trac/report/1 database] first and make sure the bug has not already been reported.  Bugs are constantly being fixed, so if you don't search first, you could easily submit a duplicate ticket for a bug that was fixed recently.  Also look through the [http://mythtv.org/pipermail/mythtv-dev/ -dev list archives], as many bugs are discussed there before they are submitted to Trac.
+
* Search the [http://code.mythtv.org/trac/report/1 bug database] first and make sure the bug has not already been reported, and do additional searches to include recently-fixed tickets.  Bugs are constantly being fixed, so if you don't search first, you could easily submit a duplicate ticket for a bug that was fixed recently.  Also look through the [http://mythtv.org/pipermail/mythtv-dev/ -dev list archives], as many bugs are discussed there before they are submitted to Trac, and [http://mythtv.org/pipermail/mythtv-commits/ -commits list archives], as any fixes should have been mentioned in commit messages.
* Include accurate description of how to recreate the problem, logs, versions (--version) and a backtrace if the bug involves a crash.
+
* Include accurate description of how to recreate the problem.  Attach (do not paste into the description) files containing logs, version information (mythbackend --version) and a backtrace if the bug involves a crash.  If reporting the bug against the MythTV Python bindings, please also attach the output of mythpython --version.
* Recompile Myth with debug symbols.  The additional information helps the developers to recognize errors.  See [http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2 HOWTO Chapter 22] for instructions.
+
* Recompile MythTV with debug symbols.  The additional information helps the developers to recognize errors.  See [[Debugging]].
* Try and make sure the error is not your misconfiguration (e.g. you don't have a certain codec installed).
+
* Try and make sure the error is not your misconfiguration.
 
* MythTV's bugs database (unlike some) is '''not''' a [[User Wish List]] or a forum for discussion of bugs.  Do not submit your feature requests there, and don't use the comments for discussion - comments are for concrete debugging information that will assist the developers to fix the bug.  Discussion belongs on the [[Mailing_List]].
 
* MythTV's bugs database (unlike some) is '''not''' a [[User Wish List]] or a forum for discussion of bugs.  Do not submit your feature requests there, and don't use the comments for discussion - comments are for concrete debugging information that will assist the developers to fix the bug.  Discussion belongs on the [[Mailing_List]].
  

Latest revision as of 21:58, 26 December 2010

MythTV now uses Trac, a popular bug-tracking system. When submitting bugs, there are a few rules and suggestions you should follow.

  • Read the Ticket HowTo and once done, read it again
  • Report bugs against the most recent unstable/development code, or failing that the latest release, and select the appropriate version under "Version" when submitting your ticket. Do not specify "Milestone", "Priority", or "Severity"--these will be filled out by the developers.
  • Search the bug database first and make sure the bug has not already been reported, and do additional searches to include recently-fixed tickets. Bugs are constantly being fixed, so if you don't search first, you could easily submit a duplicate ticket for a bug that was fixed recently. Also look through the -dev list archives, as many bugs are discussed there before they are submitted to Trac, and -commits list archives, as any fixes should have been mentioned in commit messages.
  • Include accurate description of how to recreate the problem. Attach (do not paste into the description) files containing logs, version information (mythbackend --version) and a backtrace if the bug involves a crash. If reporting the bug against the MythTV Python bindings, please also attach the output of mythpython --version.
  • Recompile MythTV with debug symbols. The additional information helps the developers to recognize errors. See Debugging.
  • Try and make sure the error is not your misconfiguration.
  • MythTV's bugs database (unlike some) is not a User Wish List or a forum for discussion of bugs. Do not submit your feature requests there, and don't use the comments for discussion - comments are for concrete debugging information that will assist the developers to fix the bug. Discussion belongs on the Mailing_List.

Once the bug is submitted, keep track of it as the developers may have additional questions or requests for you.