issue queue

There has been a lot of informal talk about Drupal’s issue queue. For designers and non-technical people, it can be a confusing place. And while there has also been some talk about creating a separate place to discuss design-related issues (for example), the simple fact is: the issue queue is where developers get informed about problems and requests and that’s the place where they organize the work that they do. If non-developers want to improve the code, they have to use the issue queue.

Following a request on the dev list, an issue and first-version code has been created to return a list of current issues as a single set of data, to be downloaded and used offline.

It includes, in a single JSON object:

• the issues, selected by project, priorities, categories, and states
• the followups/comments
• the attached files

See the issue for more detail and to submit revisions.

Give the gift of a Drupal 5 release candidate this holiday season by fixing bugs!

The Vancouver League of Drupaliers is answering the call and organizing a Drupal 5 bug hunt!

Drupal 5 is in beta 2 and will be released when all the critical bugs are dealt with. There's also non-critical bugs and each one fixed makes Drupal 5 a better release. Your help, regardless of whether you're new or a ninja, makes the release happen at the best quality possible. (More about the ways you can help here: http://drupal.org/drupal-5.0-beta2)

What's in it for you?