[development] {Short issue queues need care - 2} This week: special critical issues.

Augustin (a.k.a. Beginner) drupal.beginner at wechange.org
Sun Jun 25 12:39:25 UTC 2006

Hello and welcome to the second edition of {Short issue queues need care}.

This week:
1} Summary of featured short issue queues.
2} Report on progress since last week.
3} Why this report and how to cooperate?

1} Summary of featured short issue queues.
Pick one list. See at the very end if you wish to officially 'adopt' one 
The number in parenthesis designs the number of issues 2 weeks old or more 
(i.e. issues most likely forgotten and not being dealt with).

(Queue #1) Ready To Be Committed issues:
This one is especially for Dries, Steven, Neil and Gerhard.
25/06/2006 : 7 (2) issues only.
Dries and Steven: please note the DRUPAL-4-6 issues.

(Queue #2) DRUPAL-4-6 critical issues:
18/06/2006 : 24 (19) issues.
25/06/2006 : 8 (5) issues only.
Those are really critical issues, already fixed in head and 4.7. 2-3 
developers need to cooperate to deal with 1 issue at a time.

(Queue #3) DRUPAL-4-7 critical issues:
18/06/2006 : 31 (19) issues.
25/06/2006 : 12 (8) issues only!

(Queue #4) CVS critical bugs: 
18/06/2006 : 6 (1) issues.
25/06/2006 : 13 (1) issues only!
(slight increase since last week due to reassigning issues from stable 
branches to HEAD).

(Queue #5) DRUPAL-4-6 Patch Needs Review bugs:
18/06/2006 : 26 (25) issues.
25/06/2006 : 26 (25) issues.
Most need to be bumped to cvs, if the bug still exists. 
If the bug hasn't been fixed yet, try to reroll the patch for head, or else 
set as "patch needs work".

(Queue #6) DRUPAL-4-7 Patch Needs Review bugs:
18/06/2006 : 17 (5) issues.
25/06/2006 : 16 (7) issues only.
Make sure to note if the bug has been fixed in HEAD already: it would be silly 
to have a fix in 4.7, to see the bug reappear when 4.8 comes out.

(Queue #7)  DRUPAL-4-5 old bugs:
25/06/2006 : 5 (4) issues only.
Bump to head is the issue is still valid or close if they have been fixed.
We need to do for this old branch what has just been done for the 4.7 Beta 
releases: review each one individually, and close or bump to head as 
appropriate until no issue is left in this branch.

2} Report on progress since last week.

Remember: the number is parenthesis designs the number of old issues, i.e. 
issues over two weeks old. Those issues are probably forgotten and not being 
followed up by anyone. 
The lower the number of old issues on any one queue, the better!

Among the 10 issue lists featured last week, one of them got definitely sorted 
out: pre-4.7 betas issues:
There were 14 pages of issues when Drupal 4.7.0 came out; 8 issues left last 
week and today none remain: they have either been closed or reassigned to a 
later version.

Another dramatic change since last week is the list of critical issues:
There were 80 (56) issues last week, and only 45 (25) remain today.
The drop is mostly due to closing issues that had already been fixed or 
setting a 'normal' some issues that were not really critical.
The real critical issues still remain, and are the focus of the short issue 
queues featured this week (see above).

One area that has not seen much change is the list of issues with a patch 
needing review: 247 (202) issues last week, and 246 (207) this week.

The grand total of open issues is slightly lower this week: 1986 (1747) issues 
this week against 1992 (1758) issues last week.

3} Why this report and how to cooperate?

There are close to 2000 issues in the queue.
The figure sounds daunting: how can a very few volunteer developers deal with 
such a huge amount of bugs?

The point is that we don't need to worry of the whole issue queue, but by 
getting somewhat more organized, the most important of those issues can be 
definitively dealt with. 

To start with, there shouldn't be anything critical within the Drupal project 
issues. Critical bugs must be dealt as a matter of priority. But one can get 
easily discouraged when facing 4 four pages of critical issues. 
The first step is therefore to sort out what is really critical from what is 
Having a shortlist of what is really critical, two or three developers can 
focus on a single issue, helping each other, so that one week later there is 
one really critical issue left. Similarly, 10-12 developers could get rid of 
3-4 critical issues and in a few weeks, the list of critical issues would be 
down to almost nothing (only 1-2 issues caused by a large patch recently 
introduced in head, for example).

If you wish to participate in tackling one of the 7 short issue queues 
featured here, please reply to the list, quoting only the issue you wish to 
'adopt', changing also the subject title of your email to reflect the queue 
you have chosen. 
Hopefully, two or three more developers will reply to you, saying they want to 
help you with the issues in that same queue.

Thank you to all the volunteers for your cooperation.



Because we and the world need to change.
Intimate Relationships, peace and harmony in the couple.

More information about the development mailing list