Changes between Version 4 and Version 5 of TicketHowTo


Ignore:
Timestamp:
Oct 27, 2005, 9:36:17 PM (14 years ago)
Author:
danielk
Comment:

added link to create a ticket

Legend:

Unmodified
Added
Removed
Modified
  • TicketHowTo

    v4 v5  
    99If this is a compiling problem, e-mail the users list, then the developer list before adding a ticket. These are often caused by toolchain or dependency problems. Of course, if the problem is only present after a particular recent commit, e-mail the developer list immediately.
    1010
    11 Once you've decided to create a ticket:
     11Once you've decided to [http://cvs.mythtv.org/trac/newticket create that ticket]:
    1212 * Make sure to assign it to the GoToDev for the broken component.
    1313 * Make sure you attach logs, patches, and backtraces after you create the ticket.
    1414 * If problem causes a SEGFAULT, attach the [http://www.mythtv.org/docs/mythtv-HOWTO-21.html#ss21.2 backtrace] to the ticket.
    1515 * If you submit a patch, make sure it adheres to the [http://www.mythtv.info/moin.cgi/CodingStandards MythTV coding standards].
    16  * Please do '''not''' change a ticket's priority, severity, or milestone from the defaults.  These fields are for the person who is fixing the issue to decide.  Don't change these after the ticket's been filed, either - they'll likely just get changed back.
     16 * Please do '''not''' increase a ticket's priority, severity, or milestone from the defaults.  These fields are for the person who is fixing the issue to decide.  Don't change these after the ticket's been filed, either - they'll likely just get changed back.
    1717
    18 Tickets are generally not addressed as quickly as e-mails to the developer list, but they ensure that the problem doesn't get completely lost in the noise.
    19 
    20 If your ticket gets marked as worksforme or invalid consider this a challenge to improve the bug report. Problems often only occur with a particular setting or with some particular hardware. Figuring out what exactly is causing the problem will make it possible to reproduce the bug, which is the first step in fixing it. If the ticket is marked as invalid rather than worksforme, it probably failed some check on this checklist. Also, don't get into an arguement with whoever closed your ticket. Remember, since this person reviewed your ticket, this is the person most likely to fix your problem.
    21 
     18If your ticket gets marked as "worksforme" or "invalid" consider this a challenge to improve the bug report. Problems often only occur with a particular setting or with some particular hardware. Figuring out what exactly is causing the problem will make it possible to reproduce the bug, which is the first step in fixing it. If the ticket is marked as invalid rather than worksforme, it probably failed some check on this checklist. Also, don't get into an arguement with whoever closed your ticket. Remember, since this person reviewed your ticket, this is the person most likely to fix your problem.