On Friday, October 12, 2012 11:49:33 AM UTC+2, Jeroen De Vlieger wrote: > > > > On Tuesday, October 9, 2012 7:35:53 PM UTC+2, John Wiegley wrote: >> >> >>>>> Jeroen De Vlieger <[email protected]> writes: >> >> > But in general I'm still a bit unsure about the proper channels to >> > communicate certain stuff so that I'll get noticed. For example: * If >> I >> > encounter an bug or some oddity that I think is a bug, where exactly >> should >> > I post this information to so that it will get the attention it needs. >> > Should I post bug reports to the github issue's page? I have recently >> posted >> > two there. Or should I post them to this mailing list like I recently >> did? >> > Or should I post them to the bugtracker? >> >> > * If I have a patch to contribute a feature or fix a problem, should I >> post >> > it to this mailing list or directly to the github issues page? >> >> The best place to accumulate proposed changes to anything Ledger-related >> is >> the Bugzilla tracker at bugs.ledger-cli.org. Thanks for your >> contributions! >> >> >> > Given that I seem to have missed that and went straight to the issues page > of github, then maybe this should somehow be made more clear or > the problem can simply be prevented by disabling the github issues page (I > have no idea if that is possible though). > As long as the github issues page is alive and active, you will get people > (like me) that won't think any further and simply use this tool assuming > that it is there for a reason. > > Jeroen >
Anyhow I just made myself a bugzilla account ;-) And will be trying to reopen bug 801 because the fix posted by Craig https://github.com/jwiegley/ledger/commit/25f063ab7cb0af91891ed7e0a9948eb2e884be42 is incomplete sadly enough. Note that it's a bug report which I originally posted on the github issues page https://github.com/jwiegley/ledger/issues/83, which and is still left open there. Disabling the gitbug issues page would prevent the need to manage issues on two fronts. Jeroen Ps: in the issue I also included the patch that would fix it. Is there a means for me to push it to the repo directly thus reporting and fixing the bug at the same time or is access to the repo strictly regulated and only possible to a few people? which I would totally underdstand to be honest! Although I would suggest to try and use/review the supplied patch in those cases where one is provided ;-)
