[development] {Short issue queues need care - 7} Why we shouldn't close all issues without proper review.

[Fernando Silva]

In the last few weeks I was able to review a few hundred (about 400) issues
that were inserted in the issue tracker.

These are some thoughts:
1. People have the habit to request features for the Drupal version they
use, instead of requesting them in the HEAD.
We could have a way to stop users from adding these requests to versions
other than HEAD

2. Support requests stay months without a single response!
In my opinion there is no gain in putting support requests in the issue
tracker. A forum is the right place to discuss support, and if in some cases
these requests generate a feature or a bug report then they would be
inserted in the right place.
OTOH, if we continue to have support requests in the tracker, we should had
them a "valid for" date.(e.g. close automatically all suport requests older
than 4 weeks)

3. Patches (and bugs) stay in older queues for too long.
It seems that no one has interest in working and reviewing older patches.
I think that to have a good issue flow, we need to be more responsable in
solving ASAP older bugs and not let them increase as it happens today.

Regards,
  Fernando Silva

On 9/5/06, Dries Buytaert <dries.buytaert at gmail.com> wrote:
>
>
> On 04 Sep 2006, at 09:40, Augustin (Beginner) wrote:
> > The same scenario is repeated at each release cycle, because we, the
> > community, do not take the time to review other people's patches,
> > scratch
> > other people's itches.
>
> I agree.  I often spend 2+ hours a day reviewing patches, and when I
> post an occasional patch myself, it doesn't always get the quality
> reviews it deserves.  (I understand that my position is exceptional.)
>
> If people spent time reviewing your patches, try to return the favor,
> and review other people's patches.  Of course, you're free to do what
> you want, but it sounds like a good, social guideline.
>
> Not getting a decent review for your patch turns people off, and we
> should avoid letting this happen.  Quite the contrary, we should
> provide them with constructive reviews and help them get on board.
> Some of them will 'stick' and help review patches too.
>
> Now we're in code freeze mode, this is particularly important.  Let's
> do our best to make new people stick and to review an insane amount
> of patches together.  :)
>
> --
> Dries Buytaert  ::  http://www.buytaert.net/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20060905/5660f516/attachment.htm