Difference between revisions of "Tracker Priorities"

From PCGen Wiki
Jump to: navigation, search
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
"The code FREQ tracker should also have the target priority for release placed into the comments"
+
When a Priority 2 FREQ is moved from 'Unscheduled' to a specific release, a Dev Spec tracker needs to be created 
"As code FREQs are evaluated, those that require token definition will be set by the '''code team to priority 2'''"
+
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 
  
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.
+
The code FREQ tracker should refer to the Dev Spec Tracker, and the Dev Spec Tracker should refer to the Code FREQ
 
+
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"
 
[20:20] [Arch_SB]thpr: oh, and back in the section talking about the Dev Spec being created
 
[20:20] [Arch_SB]thpr: "The Dev Spec should point to a specification to be hosted on the PCGen Wiki."
 
[20:20] [Arch_SB]thpr: "If a specification already exists and is pointed to by the code FREQ, then that page should be used"
 

Revision as of 03:24, 29 July 2008

FREQS -

As code FREQs are evaluated, those that require token definition will be set by the code team to priority 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 tracker should refer to the Dev Spec Tracker, and the Dev Spec Tracker should refer to the Code FREQ 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