Yesterday in IRC @catch, @webchick, @xjm, and a couple others discussed possibly raising the major and critical task thresholds during code thaw, for a couple reasons:
- In order to avoid blocking features because of thresholds, some tasks are:
- Filed as "normal" when they should be "major".
- Filed as "major" when they should be "critical".
- Demoted and listed under major or critical tracking issues, even though the individual issues might still be major.
- Postponed when they should probably be active.
- Filed as features when they are more properly tasks.
All of the above have the effect of "hiding" these tasks and concealing somewhat the scope of work that remains.
- There are some tasks that can and should be addressed during feature freeze, that should nonetheless be filed and categorized properly now.
- Tasks typically take longer to complete than bugfixes, and unfixed tasks are generally less disruptive than unfixed bugs.
- We could use a little breathing room for the general health and happiness of contributors.
- Raise the critical task threshold to 25.
- Raise the major task threshold to 125.
- Recategorize "hidden" major or critical tasks appropriately, so we have a more accurate picture of D8's status.
- Do not change the bug thresholds.
- Consider lowering the thresholds again later in the cycle.
- Consensus? Make a g.d.o/core post asking for feedback.
- Update handbook documentation on the thresholds.
- Recategorize tasks where appropriate.