Home » Groups » Issue Triage

Welcome to Issue Triage!

Submitted by Paul Kishimoto on Thu, 2006-12-28 07:26
· ·

As it says in the group description:

As of December 2006, there are 1500 active issues in core and almost 10000 total active issues, giving the false impression that Drupal is buggy, unreliable and unresponsive. Join the ITWG to help counteract this!

... "ITWG" being the Issue Triage Working Group (copying the IETF is lame? yes). This is not a group for the developers who squash bugs; this is a group for the obsessive-compulsive types who don't want to contribute patches, but would like to help manage the issue queue. No one seems to be doing this at the moment, but it's a job that needs doing.

Groups.drupal.org is a good place to coordinate triage. Some of the basic activities of this group could be:

  • Maintain a how-to page or section in the Developer Handbook on triage.
  • Suggest guidelines for the issue submission form, or maintain a how-to page or section one of the Handbooks on proper issue submission (so triage isn't required)
  • Suggest improvements to project.module on an issues workflow and invalid bug states.
  • Put ourselves out of a "job" by actually herding bugs and sending unreviewed patches to some reviewers!
  • Try and get someone to start a Support Group (ha-ha) of able people to specifically handle support requests.

For example, some rules that I've figured out (by breaking):

  • Tasks and feature requests can only be against "HEAD". Currently, "HEAD" means 6.x-dev. 5.x and previous versions are in a feature freeze, because new features might break contributed modules.
  • Bugs that break the string freeze on released versions are "won't fix" because that would ruin translations.
  • Once 5.0 is released, 5.x and 4.7.x will be the only supported branches. Users submitting bugs/support requests against 4.6.x should be persuaded to upgrade.

And some suggestions too vague or principles too wide-ranging to implement:

  • "Dormant" support requests should be closed (how old is "dormant"?)
  • Bugs against x.y.z should be updated to the most recent version they apply to.
  • Duplicates should be hunted down and marked as such.
  • Unintelligible or useless bugs should be marked for more information.

Also consider the forum thread: http://drupal.org/node/103531

Allons-y!

Groups:
Issue Triage
Login to post comments