Re: [GNC-dev] What about outdated open bugs in Gnucash Bugzilla?

2019-10-27 Thread John Ralls
Colin, That's a worthwhile idea that could be easily applied to all bugs over n years old. One could start with n around 10, perhaps meaning everything against versions before 2.4.0. Care to spend some quality time in Bugzilla? Regards, John Ralls > On Oct 27, 2019, at 3:14 PM, Colin Law

Re: [GNC-dev] What about outdated open bugs in Gnucash Bugzilla?

2019-10-27 Thread John Ralls
> On Oct 27, 2019, at 2:45 PM, David Cousens wrote: > > John, > > Is there perhaps a need to place maintenance limits on GnuCash release > versions, i.e. at a specified time after release they become unsupported, > as is bugs and all. This is more than likely what actually happens in >

Re: [GNC-dev] What about outdated open bugs in Gnucash Bugzilla?

2019-10-27 Thread Colin Law
Possibly an alternative, used in Ubuntu for example, is when a version goes out of support that any bugs against that version have a comment added saying the version is out of support, saying that if the bug is relevant to a later version then please to post a comment, and marking the bug as

Re: [GNC-dev] What about outdated open bugs in Gnucash Bugzilla?

2019-10-27 Thread David Cousens
John, Is there perhaps a need to place maintenance limits on GnuCash release versions, i.e. at a specified time after release they become unsupported, as is bugs and all. This is more than likely what actually happens in practice given limited skilled developer time. As bug reports are often

Re: [GNC-dev] What about outdated open bugs in Gnucash Bugzilla?

2019-10-27 Thread Christian Gruber
Am 27.10.19 um 03:40 schrieb John Ralls: On Oct 26, 2019, at 2:34 PM, Christian Gruber wrote: Hi, I'm currently looking through the (quite long) buglist on Gnucash Bugzilla to see, where I can provide help. Unfortunatelly I'm a little bit frustrated, because

Re: [GNC-dev] Gnucash built from git doesn't start

2019-10-27 Thread John Ralls
> On Oct 27, 2019, at 3:19 AM, Lothar Paltins wrote: > > Am 25.10.19 um 21:27 schrieb Geert Janssens: >> Gnucash historically was using the autotools build system. As far as I know >> that system did put the config files in /opt/gnucash/etc/gnucash and not in / >> etc/opt/gnucash(/gnucash) >

[GNC-dev] Fwd: gnucash maint: Multiple changes pushed

2019-10-27 Thread Christopher Lam
* [new-owner-report] combined job/owner reports In addition to today's earlier new-aging-report, the experimental submenu will also have new-owner-reports i.e. customer/vendor/employee reports. These are intended to replace old reports. Rewritten, easier to maintain. Of note: * will query

Re: [GNC-dev] Gnucash built from git doesn't start

2019-10-27 Thread Lothar Paltins
Am 25.10.19 um 21:27 schrieb Geert Janssens: Gnucash historically was using the autotools build system. As far as I know that system did put the config files in /opt/gnucash/etc/gnucash and not in / etc/opt/gnucash(/gnucash) Yes, if you run "configure --prefix=/opt/gnucash". There's no

[GNC-dev] Fwd: gnucash maint: [new-aging] new receivable/payable aging reports

2019-10-27 Thread Christopher Lam
The refactored payable/receivable aging reports have been merged into maint. Of note: 1. all AP/AR accounts will be shown, each in their own currency. Every AP/AR account will get its own subtotal. 2. no more 'bad-url' errors which were caused by prepayments which were not assigned to any