Changes between Version 46 and Version 47 of TicketHowTo


Ignore:
Timestamp:
Dec 17, 2009, 3:22:36 PM (10 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TicketHowTo

    v46 v47  
    11We eventually look at all tickets. But if you go through this quick checklist before submitting the ticket, it will be addressed more quickly.
    22
    3 '''Important''' Unless you have something valuable such as a patch or further relevant debugging info, do not post a comment to an existing ticket. 'Me too' posts are strictly forbidden. Discussion about a bug or the potential fix belongs on the mailing lists and not in the ticket system.
     3'''Important''' Unless you have something valuable to add, such as a patch or further relevant debugging info, do not post a comment to an existing ticket. 'Me too' posts are strictly forbidden. Discussion about a bug or the potential fix belongs on the mailing lists and not in the ticket system, the results of the discussion may however be appended to the ticket and should be concise, dealing in facts.
    44
    55== First Steps ==
     
    1717== Opening a Ticket ==
    1818
    19 While it's not required, setting up a valid session will make any ticket you create include your name or e-mail address. To do this go to "Preferences" at the top of the page and type in your name, or even better e-mail address, then click the "Save changes" button. This can speed up the addressing of your ticket because you may be able to respond to a developers queries while they are looking at a problem rather than responding later and waiting for them to have time to look at your ticket again.
     19It is highly recommended that you set up a valid trac session which will make any ticket you create include your name or e-mail address. To do this go to "Preferences" at the top of the page and type in your name and e-mail address, then click the "Save changes" button. This can speed up the addressing of your ticket because you may be able to respond to a developers queries while they are looking at a problem rather than responding later and waiting for them to have time to look at your ticket again.
    2020
    21 Once you've decided to [http://cvs.mythtv.org/trac/newticket create that ticket]:
     21'''Important''' - Anonymous tickets will receive less attention and may in future be banned because of recent abuse by anon users.
     22
     23Once you've decided to [http://svn.mythtv.org/trac/newticket create that ticket]:
    2224 * Select the correct component from the list. (GoToDev)
    2325 * Set the version to the version you use. If you see the bug with multiple version, choose the newest. Add the output of mythfrontend --version or mythbackend --version to the ticket.
     26 * Enter a concise description of the problem along with the steps to reproduce, stick to the facts. Do NOT use hyperbole and do NOT make threats, show respect for the person who will spend their times triaging the ticket or fixing the bug, failure to follow these rules will make it likely that your ticket will go ignored.
    2427 * Make sure you attach logs, patches, and backtraces after you create the ticket.
    2528 * If problem causes a SEGFAULT, attach the [http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2 backtrace] to the ticket.