[GNC] balance of interests between users and developers

Carsten Hütter carsten.huetter at gmx.de
Sat May 20 19:36:07 EDT 2023


Hello Gyle!

It's not that hard to install and run two (ore more) gnucash versions
in the Windows environment side by side. Just rename the gnucash program folder to e. g. "gnucash 5.1-15 nightly" (or any other name that seems appropriate). Then start a different gnucash setup. A new "gnucash" folder will be created in the program directory. You can navigate to the preferred gnucash folder to get the application started, and you can create an appropriate link on your desktop or start menu for easier access. BTDT.

Greetings

Carsten
⁣

Am 20. Mai 2023, 23:57, um 23:57, Gyle McCollam <gmccollam at live.com> schrieb:
>If the new version could be installed alongside the current version and
>data files kept separate, I for one would be happy to enter my
>transactions in both the new and old to test the new.  However, since
>the warnings are to not use for production or live data, I don't test
>the new.  I wouldn't know how to do that in Windows, but it would be
>nice to be able to do that.
>
>
>Thank You,
>
>Gyle McCollam
>
>Gyle McCollam
>
>gmccollam at live.com<mailto:gmccollam at gyleshomes.com>           email
>
>________________________________
>From: gnucash-user <gnucash-user-bounces+gylemc=gmail.com at gnucash.org>
>on behalf of Michael or Penny Novack <stepbystepfarm at comcast.net>
>Sent: Saturday, May 20, 2023 5:25 PM
>To: gnucash-user at gnucash.org <gnucash-user at 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 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 of software
>development". In the work world I came from, about 20% of the project
>time was at the start formalizing the requirements (what is this thing
>supposed to do). So yes, we business analysts and systems analysts took
>part in that phase, but mainly asking questions of the clients/users
>"OK, but what do you want it to do in THIS situation?" << because
>initially, all the clients/users picture is how it is to work normally
>-- NOT picturing all the rare cases/exceptions that might come up --
>and
>roughly 80% of the code will end up being what handles these odd
>situations >>
>
>THEN maybe 30% of the time to make really formal definition and spec it
>out and 30% to code it.
>
>But at the end, the clients/users need to come back to provide the
>testers, the final 20%. In other words, about 40% of the time
>commitment
>would not be us analysts and programmers but USERS.
>
>Of course in that "world" the users were there because they were being
>paid to be there just like we analysts/programmers were. Sorry, but in
>this voluntary environment I am NOT seeing the users who are saying
>that
>they want thus and ALSO saying ":and to get that, we will commit to our
>part of the project"
>
>
>Michael D Novack
>
>
>_______________________________________________
>gnucash-user mailing list
>gnucash-user at gnucash.org
>To update your subscription preferences or to unsubscribe:
>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-user mailing list
>gnucash-user at gnucash.org
>To update your subscription preferences or to unsubscribe:
>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.



More information about the gnucash-user mailing list