CCB sees all tickets classified as bugs. For CCB to see a Task, Improvement, or New Feature request, you must use the Label CCB. To see the items currently waiting for CCB, see the CCB Filter.
CCB decisions are made during weekly GMAT meetings, at scheduled CCB meetings, or when appropriate via email/electronic discussions. Early in a release cycle, formal CCB meetings are scheduled bi-weekly, late in the release cycle CCB may occur weekly and possibly daily. CCB meetings are based on need and not held when not needed. Decisions are marked as CCB on the ticket.
When ideas are brought to CCB, they are coarsely prioritized for consideration in the next release, they may be closed as something that will never be performed given the current goals of the project, or are put in the backlog for consideration in future releases. To see the items currently waiting for CCB, see the CCB Filter. If a ticket is denied action or is not planned for attention in the “near” future, the FixBy field is set to Someday. If CCB decides to take action on the ticket, FixBy is set to the next release and priority is set to either P1 or P2. P1 and P2 are defined below with representative examples.
There are times when many issues (hundreds) requiring triage. Below is our approach for triaging large quantities of issues in a timely manner.
The GMAT CCB is composed of senior project members (and soon customer representatives) that ensure a broad range of expertise on the board. Decisions are usually delegated to a subset of CCB members with expertise in the area regarding decision to be made.