By Roy on

The feature request list is so long and so many entries are not assigned ... should I bother making new entries??

Here's a reminder to a nearly 1 year old productivity suggestion: http://drupal.org/node/view/157

Comments

adrian’s picture

adrian commented

I would really love to help clearing up the bugs list of items that aren't pertinent anymore.

I believe having a 'pure' stream of information would be a lot more helpfull than having 91 open bugs .. some of which have been fixed but never closed .. etc.

I am just afraid that actual new bugs might get lost in that jungle.

Dries’s picture

Dries commented

It is my impression that the bug list is maintained reasonably well.

Though we should probably look at all bugs and feature requests filed against Drupal 3.0.0 and Drupal 4.0.0 and either close or update them. Seeing lots of bugs filed against Drupal 4.0.0 makes people think the bug list gets forgotten.

Maybe some problems can be solved by improving the visual design of the project pages (eg. overview of last or most active bug reports, different sort order, seperation between core and contributed modules/themes)?

Also, what do you mean with a "pure stream of information"?

Dries’s picture

Dries commented

Sure. Add new feature requests as you see fit as long you don't duplicate another entry. If a particular feature request is already there, feel free to add additional information.