On 12/28/2023 3:56 AM, G R Hewitt wrote:
My two pennyworth is similar.
My two cents is a little different.
Also a retired pro, a very senior sort of systems analyst who toward the
end mainly handling what had the department programmers stumped or was
beyond them in the first place.
This is a CHOICE. Do you immediately upgrade to the newest version or do
you wait long enough for the new version bugs to be found and corrected?
Do you like being on the "bleeding edge" or not? Do you NEED some
feature that has been added with the new version?
With a full testing protocol, a new version would spend some tine in
"beta" with only designated "beta testers" using it (experienced users
who would report bugs to the development team, people able to identify
actual bugs from things that simply might require explanation what some
new feature does and doesn't do). This project does NOT have a large
enough "testing budget", nothing like what I used to have available to
me (around 20% of the total new system budget). Lack of a user/tester
base is why I am not helping with development.
So I'll put it plainly. If you don't need a new feature of a new
version, and if you dislike being an involuntary beta tester (during
this initial unofficial beta period) then wait a little while before
upgrading. Monitor this list for the complaints about the new version
and upgrade only when these have died down. Skip ever upgrading to
versions that were particularly buggy. Yes, you will likely always be
one or two versions behind the newest, but you won't be complaining.
Michael D Novack
_______________________________________________
gnucash-user mailing list
gnucash-user@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.
