Changes between Version 29 and Version 30 of KeywordGuide


Ignore:
Timestamp:
07/26/09 17:43:38 (10 years ago)
Author:
magnate
Comment:

Added "blocker"

Legend:

Unmodified
Added
Removed
Modified
  • KeywordGuide

    v29 v30  
    11= Using keywords in tickets = 
    22 
    3 Angband is a big program. There are many thousand lines of code, and dozens of different things to consider when working on it. With a few exceptions (like the maintainer), most developers are interested in specific aspects of the code (user interface, item generation, vaults, savefile handling, whatever). Using keywords in your tickets helps them find the tickets they're interested in more easily, and makes it more likely that your ticket will receive attention. 
     3Angband is a big program. There are over a hundred thousand lines of code, and dozens of different things to consider when working on it. With a few exceptions (like the maintainer), most developers are interested in specific aspects of the code (user interface, item generation, vaults, savefile handling, whatever). Using keywords in your tickets helps them find the tickets they're interested in more easily, and makes it more likely that your ticket will receive attention. 
    44 
    55It's not quite as easy as it sounds. Obviously the worst thing you can do is use no keywords at all, but using too many keywords, and using the wrong ones, are both almost as bad. So the standard keywords you should use are listed below, along with the issues they cover. If your ticket touches on any of these issues, please use the relevant keywords. (The list is not perfect, so please check this page periodically in case it's been improved.) 
     
    7272== Other keywords == 
    7373 * meta --  special keyword meaning that this ticket is a consolidation or list of other tickets, not an issue in its own right 
     74 * blocker --  used by Takkaria to mean "do not release until this is fixed"