Bug squishing questions.

[Derek Atkins]

Hi,

Ryan Claycamp <ryanc at gemair.com> writes:

> Last night I went through the bugs to see if I could help out.  I'm
> not a programmer, but would like to give back somehow.  I noticed
> today that two of them were closed.

Well, I closed a few that were marked "non-reproducible".  That's
what's supposed to happen.

> Today I thought I'd give it another go and did a search on old version
> bugs and found one against 1.4.x, #116018
> <http://bugzilla.gnome.org/show_bug.cgi?id=116018>.  However, the
> information clearly shows that it is a 1.8.x bug.  Should I report
> that through Bugzilla or just mention it here to get it reassigned?

This isn't a gnucash bug.  It's a bug in the upstream m4 script(s).
You should report them to intltool and libtool, respectively.  There
is nothing that gnucash can do about this.

> What are good ways to get bugs closed that do not provide enough
> information?  I found some where information was asked for months ago
> and nothing was provided.  Should a new comment be filed to bring the
> bug back to the attention of the programmers?  Or something else?

Usually a comment will suffice.  Not always.  Sometimes you may need a
comment in the bug report, wait a few days, and then post something
here or in IRC.

> I enjoy GnuCash very much and would like to help what like ways I can.

Thanks.  Tackling the bug reports is EXTREMELY helpful!

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available