== 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.

Tickets only applicable to the indicated OS release(s):

  * [query:status=!closed&keywords=~legacy-os legacy-os] \\Applies to any operating system that is no longer officially supported by MacPorts. 
  * [query:status=!closed&keywords=~tiger tiger]
  * [query:status=!closed&keywords=~leopard leopard]
  * [query:status=!closed&keywords=~snowleopard snowleopard]
  * [query:status=!closed&keywords=~lion lion]
  * [query:status=!closed&keywords=~mountainlion mountainlion]
  * [query:status=!closed&keywords=~mavericks mavericks]
  * [query:status=!closed&keywords=~yosemite yosemite]
  * [query:status=!closed&keywords=~elcapitan elcapitan]
  * [query:status=!closed&keywords=~sierra sierra]
  * [query:status=!closed&keywords=~highsierra highsierra]
  * [query:status=!closed&keywords=~mojave mojave]
  * [query:status=!closed&keywords=~catalina catalina]
  * [query:status=!closed&keywords=~bigsur bigsur]
  * [query:status=!closed&keywords=~monterey monterey]
  * [query:status=!closed&keywords=~ventura ventura]
  * [query:status=!closed&keywords=~sonoma sonoma]

Tickets only applicable when using the indicated `build_arch`:

  * [query:status=!closed&keywords=~ppc ppc]
  * [query:status=!closed&keywords=~ppc64 ppc64]
  * [query:status=!closed&keywords=~i386 i386]
  * [query:status=!closed&keywords=~x86_64 x86_64]
  * [query:status=!closed&keywords=~arm64 arm64]
  * [query:status=!closed&keywords=~LP64 LP64] \\
    The ticket describes a problem caused by the size of variables of type int, long or pointers on a 64-bit arch.

Tickets only applicable with patches:

  * [query:status=!closed&keywords=~haspatch haspatch] \\
    The ticket has a patchfile attached that may be ready to apply. It can also mean that a GitHub pull request exists. 
  * [query:"status=!closed&keywords=~haspatch maintainer" haspatch maintainer] \\
    The ticket has a patchfile attached that was approved or supplied by the port maintainer that may be ready to apply.

Tickets that depend on others:

  * [query:status=!closed&keywords=~upstream upstream] \\
    The problem report was escalated to upstream and is waiting for response or the next release.

Tickets fixing security vulnerabilities:

  * [query:status=!closed&keywords=~security security]

The ticket is only applicable when building the `+universal` variant of a port:

  * [query:status=!closed&keywords=~universal universal]

The ticket is only applicable when running port in `trace mode` (-t):

  * [query:status=!closed&keywords=~tracemode tracemode]

Tickets for base that have been fixed but still need to be backported to a release branch:

  * [query:status=closed&keywords=~needs-backport needs-backport]\\
    This keyword should be removed when backporting to the current release branch. The milestone field should be set to a milestone for the release branch when backporting.

{{{
#!comment
TODO: find out how to do a query for "leopard" that does NOT also include "snowleopard", for "lion" that does NOT also include "mountainlion", for "sierra" that does NOT also include "highsierra", and for "ppc" that does NOT also include "ppc64"
}}}