Help needed on the bug reports on gnucash reports?

[Christian Stimming]

Hi Carsten,

thanks a lot for all the work on the bugreports so far.

It is up to you which step to do next. Personally, I'd pick the enhancements 
that align with your personal wishes, and do those...

Regards,

Christian

Am Dienstag, 7. Mai 2013, 23:53:38 schrieb Carsten Rinke:
> Hi Geert,
> 
> meanwhile I have started walk through the open bugs on the reports and
> hope to conclude it by next week (currently I cannot continue as I am on
> travel).
> 
> I start wondering what comes after:
> - I could start trying to work on some of the bugs
> - I could start working on the report documentation in order to have a
> baseline to judge if something really is a bug
> - I could continue picking any enhancement that comes closest to my
> current personal wish and simply try to implement it
> - etc.
> 
> Is there a rule set that helps avoid double work and let's me pick the
> right thing first?
> Especially regarding enhancements: Who can decide if something is an
> enhancement or not before someone starts implementing it?
> 
> Thanks,
> Carsten
> 
> On 03/26/2013 06:46 PM, Geert Janssens wrote:
> > [ Reposted from another mail address. Sorry if you received this mail
> > twice ]
> > 
> > Hi Carsten,
> > 
> > Thank you for your offer to help us with the bug reports.
> > 
> > In addtition to your proposed suggestions, I would also like to add:
> > - if there's not enough information to reproduce a bug, ask the original
> > reporter for more details. Often a gnucash trace file helps already (1)
> > - in general make sure a bug report is complete: is the platform given
> > (linux/windows/mac, 32 bit/64bit, what happened, does it happen alway,
> > how to reproduce,...)
> > - find duplicate bugs and mark them as such
> > - ...
> > 
> > The other developers may has some additional suggestions.
> > 
> > Note that I have moved your question to the gnucash-devel mailing list
> > since it is development related.
> > 
> > Thanks again for volunteering.
> > 
> > Geert
> > 
> > 
> > (1) Where to find the gnucash trace file depends a bit on the user's
> > platform. Here is a link I usually provide to the bug submitters for
> > more details: http://wiki.gnucash.org/wiki/Tracefile
> > 
> > On Monday 25 March 2013 19:34:23 Carsten Rinke wrote:
> >> Hi,
> >> 
> >> I just browsed through some of the bug reports about GnuCash reports.
> >> Looks like some bugs have been confirmed but are still in status
> >> unconfirmed since ages (and similar issues).
> >> 
> >> It seems, there is some cleanup needed, e.g. closing old and not
> >> reproducable bugs, re-classifying reported bugs into enhancement
> >> requests etc.
> >> 
> >> How can I help with that?
> >> Carsten
> >> _______________________________________________
> >> gnucash-user mailing list
> >> gnucash-user at gnucash.org
> >> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> >> -----
> >> Please remember to CC this list on all your replies.
> >> You can do this by using Reply-To-List or Reply-All.
> 
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel