Last updated January 26, 2016. Created on June 27, 2011.
Edited by xjm, kevinwalsh, JohnAlbin, webchick. Log in to edit this page.

Note that this page is not up to date with the most recent core policies for managing technical debt. See the Allowed changes during the Drupal 8 release cycle and the release cycle overview for more up-to-date information.

Drupal core's issue thresholds are used to manage technical debt. During Drupal 8's development, feature completion and clean-up phases, the issue thresholds were:

(Earlier in the release cycle, Drupal 7 issues also counted toward Drupal 8 issue thresholds.)

When the issue thresholds are exceeded, core temporarily enters a period of restricted development:

  • New features will not be committed, since new features tend to add technical debt.
  • Relatively minor patches that touch a lot of files (e.g., coding standards clean-ups) will also not be committed until thresholds are met, to ensure that more urgent bug fixes are able to target a relatively stable code base.

As soon as issue counts are again under thresholds, these patches can be accepted again. This means that the best way to get a feature in is to help keep major and critical counts down.

For more information, see the explanation of the Drupal core release cycle and frequently asked questions.

Frequently asked questions

See the release cycle FAQ.

Looking for support? Visit the forums, or join #drupal-support in IRC.