[development] How to post bug reports and patches

Tomas Fulopp tomi at vacilando.org
Fri Oct 31 16:42:50 UTC 2008

Greg, you've won a bet I did with myself that at least one person on this
list would return to me with my own deficiencies :-)
Yes, the BG issue queue is long as I am swamped with other deadlines. The
thing you do not know is that I have not forgotten or given up on it, that
it worries me, that I am grateful for every other person who helps me in
there, that I will, definitely will, deal with anything outstanding in there
as soon as I can.

Your post however missed the larger point I carefully formulated in my post.

On Fri, Oct 31, 2008 at 4:14 PM, Greg Knaddison - GVS <
Greg at growingventuresolutions.com> wrote:

> On Fri, Oct 31, 2008 at 6:10 AM, Tomas Fulopp <tomi at vacilando.org> wrote:
> > I think it is not enough to be just defensive and say core maintainers
> are
> > busy with Drupal 7 (thousands of people are using D5 and D6), advise to
> Ok, let's accept your argument that it's not enough.  So, what do we do?
> How would you say that you've solved the problem in your own queue(s)?
> http://drupal.org/project/issues/brilliant_gallery?projects=171445&states=8
> I'd say that you haven't.  Patches there are sitting for almost a
> _year_ in code needs review without response.
> Neither on the large scale nor on the small scale do we have a simple
> solution to this problem.  There's been lots of great advice in this
> thread and amongst it all lies the basic answer: it takes work.
> Regards,
> Greg
> --
> Greg Knaddison
> Denver, CO | http://knaddison.com | 303-800-5623
> Growing Venture Solutions, LLC | http://growingventuresolutions.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20081031/8924892d/attachment.htm 

More information about the development mailing list