Tickets related to relevant milestones

• Previous?: Tickets associated with the previous milestone
• Next?: Tickets associated with the next planned milestone
• Unplanned?: Tickets associated with the next planned milestone

Tickets in various stages of development

• Described: Tickets that have been roughly described but not in sufficient detail to know how they would be implemented or what they would affect.
• Specified?: Tickets that have been fully specified, such that they could be implemented.
• In progress?: Tickets that have been begun, generally in a branch (since only short tickets should be worked on in HEAD, and short tickets wouldn't bother being marked with this tag).
• Implemented?: Tickets that have been implemented but not tested. This essentially always means a patch is attached to the ticket with no test code
• Tested?: Tickets that have a patch attached with test code included. Note that tickets that once this patch is applied, the tickets are just closed, rather than being tagged with something like 'done'.

Tickets of varying complexity

• Easy: Tickets that are very easy, such that the test code is likely to be more complicated than the actual fix.
• Medium?: Tickets of a wide variety, but generally tractable by a single person in a single session.
• Hard?: Tickets that have either complicated design decisions to make or that require significant amounts of code. These should nearly always be done in a branch.

Tickets in various approval states

• Proposed?: Tickets (generally features) that have been proposed but not assessed.
• For?: A generally favorable rating, but not necessarily a commitment that patches will be accepted. Most likely, implementation details would be the deciding factor.
• Against?: A generally disfavorable rating, but a stellar implementation could persuade. This rating should carry notes as to why the ticket is unfavorable along with clear concerns that could possibly be addressed.
• Approved?: An accepted feature, meaning that patches would be accepted that provided this feature.
• Denied?: A denied feature. Reasons must be given for this categorization.

Tickets that will affect backward compatibility

• Affects?: The ticket has some affect on backward compatibility, but it can generally be resolved through a combination of warnings and internal hacks.
• Breaks?: The ticket breaks backward compatibility. It will only be allowed in relatively major revisions.