| | 1 | == Choosing good keywords for tickets == |
| | 2 | |
| | 3 | 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. |
| | 4 | |
| | 5 | ||'''Keyword'''||'''Meaning'''|| |
| | 6 | || `haspatch` || The ticket has a patch attached which the submitter believes will fix the bug or implement the enhancement. || |
| | 7 | || `maintainer` || The ticket contains a patch from the port's maintainer, and can thus be acted upon immediately. || |
| | 8 | || `tiger`/`leopard`/`snowleopard` || The ticket is only applicable to the indicated OS release(s) || |
| | 9 | || `i386`/`x86_64`/`ppc`/`ppc64` || The ticket is only applicable when using the indicated build_arch || |
| | 10 | || `LP64` || The ticket is only applicable when building for a 64-bit arch || |
