Difference between revisions of "Tracker Priorities"
LegacyKing (talk | contribs) (New page: FREQS - When making a FREQ (Code) you need to determine whether or not it is fully spec'd out. If it is not spec'd then you need to set the tracker priority to #2 (Means needs specs). Whe...) |
LegacyKing (talk | contribs) |
||
| Line 1: | Line 1: | ||
FREQS - | FREQS - | ||
| − | + | All Code FREQs will be made and left at the Default level of 5, and placed in the unscheduled category, unless it was specified for another group. "As code FREQs are evaluated, those that require token definition will be set by the '''code team to priority 2'''" | |
| + | |||
| + | When the FREQ comes up for discussion a Dev Spec Tracker will be made and a link to a Wiki page with the particulars of the FREQ. | ||
Revision as of 03:18, 29 July 2008
FREQS -
All Code FREQs will be made and left at the Default level of 5, and placed in the unscheduled category, unless it was specified for another group. "As code FREQs are evaluated, those that require token definition will be set by the code team to priority 2"
When the FREQ comes up for discussion a Dev Spec Tracker will be made and a link to a Wiki page with the particulars of the FREQ.
