Difference between revisions of "Tracker Priorities"
| Line 5: | Line 5: | ||
Use of Development Spec Trackers | Use of Development Spec Trackers | ||
| − | * When a Code FREQ tracker is created, its priority will be set to 5, as the default, and will be placed in the 'Unscheduled' category unless otherwise directed by the Code SB or 2nd. | + | * When a Code FREQ tracker is created, its priority will be set to '''5''', as the default, and will be placed in the 'Unscheduled' category unless otherwise directed by the Code SB or 2nd. |
* As the Code Team evaluates the Code FREQs, the priority for the trackers for those FREQs that require token definition will be set to '''2'''. | * As the Code Team evaluates the Code FREQs, the priority for the trackers for those FREQs that require token definition will be set to '''2'''. | ||
* When a Priority 2 FREQ is moved from 'Unscheduled' to a specific release, a Dev Spec tracker needs to be created. | * When a Priority 2 FREQ is moved from 'Unscheduled' to a specific release, a Dev Spec tracker needs to be created. | ||
| Line 12: | Line 12: | ||
* The Code FREQ and Dev Spec trackers should cross-reference each other. | * The Code FREQ and Dev Spec trackers should cross-reference each other. | ||
* The code FREQ tracker should also have the target priority for release placed into the comments. | * The code FREQ tracker should also have the target priority for release placed into the comments. | ||
| − | * The priority of the FREQ should not be set to a value above 2 until the Dev Spec is closed by the data team. | + | * The priority of the FREQ should not be set to a value above '''2''' until the Dev Spec is closed by the data team. |
* When the Dev Spec tracker is closed, the Code FREQ should be raised to the target priority shown in the comments | * When the Dev Spec tracker is closed, the Code FREQ should be raised to the target priority shown in the comments | ||
Revision as of 04:01, 29 July 2008
Tracker Priorities and Standards for Entries:
--
Use of Development Spec Trackers
- When a Code FREQ tracker is created, its priority will be set to 5, as the default, and will be placed in the 'Unscheduled' category unless otherwise directed by the Code SB or 2nd.
- As the Code Team evaluates the Code FREQs, the priority for the trackers for those FREQs that require token definition will be set to 2.
- When a Priority 2 FREQ is moved from 'Unscheduled' to a specific release, a Dev Spec tracker needs to be created.
- The Dev Spec should point to a specification to be hosted on the PCGen Wiki.
- If a specification already exists and is pointed to by the code FREQ, then that page should be used.
- The Code FREQ and Dev Spec trackers should cross-reference each other.
- The code FREQ tracker should also have the target priority for release placed into the comments.
- The priority of the FREQ should not be set to a value above 2 until the Dev Spec is closed by the data team.
- When the Dev Spec tracker is closed, the Code FREQ should be raised to the target priority shown in the comments
