[GNC-dev] Bugzilla cleanup

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GNC-dev] Bugzilla cleanup

GnuCash - Dev mailing list
Hi All,
I saw a note on the irc channel the other day about trying to do some triage on the open bugs and clean them up.  Before I start testing and changing statuses without anyone knowing who I am, I figured I would send an email first.  I have been a user of gnucash for about 5 or 6 years now and been attempting to learn some of the code base by reading every commit as they are applied.  I will admit most of my programming background is in vba and vb.net, so the c/c++ is understandable to me, but I get lost when I see the scheme code.  I hope to get more involved as time moves on maybe trying to fix some of the simpler bugs, but for now, I feel like I can test some of them and do some general cleanup without too much objection.
To make sure I'm on the right track, one of the first bugs I came across was https://bugs.gnucash.org/show_bug.cgi?id=797151.  If I look at this, I believe it should be marked as applying to Gnucash, not bugzilla.  Given the comment has the original reporter indicated that he has solved the problem, I might also be tempted to change it to Resolved > Incomplete or Resolved > Notabug, but I could see where there is still a bug but I don't know if there is enough interest to keep it open for that.
My goal is to just help the project out, so if there is any other guidelines someone wants me to follow, I'd be quite grateful.
Thanks,Matt
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Reply | Threaded
Open this post in threaded view
|

Re: [GNC-dev] Bugzilla cleanup

Frank H. Ellenberger-3
Hello and welcome on board, Matt!

Am 10.04.19 um 03:32 schrieb Matthew Forbis via gnucash-devel:
> Hi All,
> I saw a note on the irc channel the other day about trying to do some triage on the open bugs and clean them up.  Before I start testing and changing statuses without anyone knowing who I am, I figured I would send an email first.  I have been a user of gnucash for about 5 or 6 years now and been attempting to learn some of the code base by reading every commit as they are applied.  I will admit most of my programming background is in vba and vb.net, so the c/c++ is understandable to me, but I get lost when I see the scheme code.  I hope to get more involved as time moves on maybe trying to fix some of the simpler bugs, but for now, I feel like I can test some of them and do some general cleanup without too much objection.
> To make sure I'm on the right track, one of the first bugs I came across was https://bugs.gnucash.org/show_bug.cgi?id=797151.  If I look at this, I believe it should be marked as applying to Gnucash, not bugzilla.  Given the comment has the original reporter indicated that he has solved the problem, I might also be tempted to change it to Resolved > Incomplete or Resolved > Notabug, but I could see where there is still a bug but I don't know if there is enough interest to keep it open for that.

Right, should be
Product: GnuCash,
Component: Backend - SQL


> My goal is to just help the project out, so if there is any other guidelines someone wants me to follow, I'd be quite grateful.
> Thanks,Matt
_______________________________________________
gnucash-devel mailing list
[hidden email]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel