<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ryan Claycamp wrote:
<blockquote cite="mid20040713233315.GB24856@gemair.com" type="cite">
<pre wrap="">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.
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
<a class="moz-txt-link-rfc2396E" href="http://bugzilla.gnome.org/show_bug.cgi?id=116018"><http://bugzilla.gnome.org/show_bug.cgi?id=116018></a>. 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?
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?
I enjoy GnuCash very much and would like to help what like ways I can.
Ryan
</pre>
</blockquote>
Ryan, I am in the process of going through the bugs as well. You may
like to read the thread regarding this effort from last month. Look
for the thread<a
href="https://lists.gnucash.org/pipermail/gnucash-user/2004-June/010632.html">
scheduled transactions make bad transactions with 1.8.9 </a>and Bug
Triage. I am going through the list from oldest to newest and add
myself as a CC where I've added co<br>
<br>
My first goal is to have read all of the bugs to identify possible
duplicates. Those bugs that I can identify as bugs (rather then
enhancement requests) I am trying to reproduce on my system running GC
1.8.9 and comment on what I find or request additional information.
I'm still trying to get my feet wet with this but eventually we would
want to come up with a standard procedure on how to deal with a bug
that can not be reproduced, doesn't get any response from the reporter,
etc.<br>
<br>
Currently, I am going through the list from oldest to newest and I'm
adding myself as a CC when I'm commenting on a bug. You might want to
do the same going through the list from newest to oldest.<br>
<br>
<pre class="moz-signature" cols="72">--
Thanks
Volker Englisch
<a class="moz-txt-link-freetext" href="mailto:Volker@Englisch.us">mailto:Volker@Englisch.us</a> (h)
</pre>
</body>
</html>