Changes between Version 15 and Version 16 of TracTicketing


Ignore:
Timestamp:
Jan 3, 2009, 5:59:44 AM (15 years ago)
Author:
raimue (Rainer Müller)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TracTicketing

    v15 v16  
    1 = A. Before you file a ticket .... =
    2 
    3 == 1. Check the Problem HotList ==
    4 
    5 The [wiki:ProblemHotlist Problem HotList] contains possible solutions to problems that affect many MacPorts users.  If a solution to your problem listed there works, don't file a ticket.
    6 
    7 == 2. Search to see if a Trac ticket has already been filed. ==
    8 
    9 Avoid filing duplicate bugs.  Search for duplicates by:
    10  * using the search bar that appears on each page;
    11  * using [http://trac.macports.org/projects/macports/search the search page];
    12  * browsing the list of [report: categorised reports]; or
    13  * making an advanced search by constructing a [http://trac.macosforge.org/projects/macports/query custom query].
    14 
    15 == 3. Is the problem an application error and not related to compiling and installing? ==
    16 
    17 In general, application bugs should be reported to the developers of the app ("upstream"), not MacPorts.  An application bug that affects a large number of MacPorts users might merit a MacPorts bug for informational purposes only, but this should be done sparingly.
    18 
    19 == 4. Is the problem with a 'port upgrade' operation? ==
    20 
    21 If so, try a 'port uninstall foo' and then reinstall.  You might also want to run 'port -fR upgrade foo' to rebuild ports depending upon port foo.
    22 
    23 = B. How to file a ticket =
    24 
    25 Look at our [http://guide.macports.org/#project.tickets official ticketing guidelines] for up-to-date information on how to file proper tickets.
    26 
     1This wiki page has been moved into the [http://guide.macports.org/#project.tickets MacPorts Guide]. Please change any links to point there directly.