Or just fire up your OS's favourite hypervisor (Hyper-V for Windows, KVM on
Linux, etc) and run multiple instances.
In fact, with a single Windows VM, you can keep a tree of alternate
realities (i.e., checkpoints), and jump back and forth between different
scenarios. For example, running 4.10, you
;
>From: gnucash-user
>on behalf of Michael or Penny Novack
>Sent: Saturday, May 20, 2023 5:25 PM
>To: gnucash-user@gnucash.org
>Subject: Re: [GNC] balance of interests between users and developers
>
>Precisely because I am a retired pro, I ha
Sent: Saturday, May 20, 2023 5:25 PM
To: gnucash-user@gnucash.org
Subject: Re: [GNC] balance of interests between users and developers
Precisely because I am a retired pro, I have not worked on development
in this volunteer environment.
See, my experience was in a different environment when
Precisely because I am a retired pro, I have not worked on development
in this volunteer environment.
See, my experience was in a different environment when we had end user
commitment to the project. By which I mean end user TIME. Not "I want"
but "I am willing to commit to the end user part o
On 20/05/2023 20:05, Vincent Dawans wrote:
In my (long gone) days as a paid software
developer, we had access to a QA/test team that would give us all the
feedback we needed.
In my own (also long gone) days as a software developer I remember
reading a (partly) humorous article that reckoned t
On 2023-05-20 12:05, Vincent Dawans wrote:
> When you compile from source on Linux in particular, as a developer this is
> super easy and allows you to install as many versions of gnucash
> concurrently as you want. However I don't think it's possible to install
> concurrent versions from official
I think Geert puts the issue clearly in highlighting the need for more
testing, a weak spot in any open source software. This is even more so with
gnuCash because we are dealing with critical financial data, both in terms
of the importance of testing but also the challenge since we don't want
users
Thank you Geert, for a considered response and reminder of the limitations of
a (all?) volunteer groups.
I can imagine that it was disheartening for the dev team to be met with so
many bugs and so much vitriol over the issues some use-cases found with the
5.0 release. I can also understand the
I really shouldn't answer this, but it's too painful to read...
Perhaps the user's expectations are too high for a volunteer project such as
gnucash. It's
true, things go wrong. Especially with major releases which typically have
changes
accumulating over the longer development cycle which get
I agree with the sentiments WM expressed; I have had the growing feeling
from reading the emails that pet projects are worked on in isolation to the
main.
It kind of reminds me of a model railway exhibition I once went to many
moons ago. On one large display, all nicely set out, no trains were runn
10 matches
Mail list logo
