Version 6 (modified by cooljeanius (Eric Gallager), 11 years ago) (diff) |
---|
Choosing good keywords for tickets
Trac can search the full text of tickets, so adding a keyword that already occurs in another field doesn't help for general searching. If we standardise the use of certain keywords, however, it could make finding certain specific types of ticket much easier. This, then, is a suggested list of keywords that we might like to standardise.
Keyword | Meaning |
---|---|
haspatch | The ticket has a patch attached which the submitter believes will fix the bug or implement the enhancement. |
maintainer | The ticket contains a patch from the port's maintainer, and can thus be acted upon immediately. This keyword is intended to be used along with the haspatch keyword.
|
tigerleopard snowleopard lion mountainlion | The ticket is only applicable to the indicated OS release(s). |
i386 x86_64 ppc ppc64 | The ticket is only applicable when using the indicated build_arch .
|
LP64 | The ticket describes a problem caused by the size of variables of type int, long or pointers on a 64-bit arch. |
lack-of-interest | Tickets with keyword lack-of-interest set and older than 3 days can probably be closed as nobody seems to be interested anymore. If the ticket is later re-opened due to a renewed interest in it, be sure to remove the lack-of-interest keyword. |
needs-review needs-testing | Intended to use for tickets against base which will add new features. |