Tracker Priorities

Code Bug and FREQ Tracker Priorities

Priority	Priority Description
9
8
7
6
5	New Dev Spec. This Dev Dpec is under review or is waiting for assignment.
4
3
2
1

Development Spec Tracker Priorities

Priority	Priority Description
9
8
7
6
5	New Dev Spec. This Dev Dpec is under review or is waiting for assignment.
4
3
2
1

Use of the Dev 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

Doc Bug and FREQ Tracker Priorities

Priority	Priority Description
9	Doc FREQ is critical for the next release.
8	Doc FREQ is critical for the next stable release.
7	Doc FREQ is highly desirable for the next stable release.
6	Documentation FREQ has been assigned and is being worked.
5	New Documentation Feature Request. This Doc FREQ is under review or is waiting for assignment.
4	Doc FREQ requires additional definition.
3	Doc FREQ waiting for code work. Reference code tracker.
2	Reserved
1	Reserve