Tracker Priorities

Tracker Priorities and Standards for Entries:

--

Use of Development Spec Trackers

• All newly created FREQ trackers will be left at default of 5, and placed in the 'Unscheduled' category, unless directed to do otherwise by the Code SB or 2nd.
• 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