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

Johan Forngren johan at forngren.com
Tue Sep 5 15:40:58 UTC 2006

Feature requests that's not gonna make it into core should also be an 
own category.

Also I don't think we should have a "valid date", since then people will 
have to bump their issues over and over again...

introfini wrote:
> I think ideas #1 and #2 are definitely very welcome.
> Regards,
> introfini
> ________________________________
> From: development-bounces at drupal.org [mailto:development-bounces at drupal.org]
> On Behalf Of Fernando Silva
> Sent: Tuesday, September 05, 2006 4:13 PM
> To: development at drupal.org
> Subject: Re: [development] {Short issue queues need care - 7} Why we
> shouldn'tclose all issues without proper review.
> 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/

More information about the development mailing list