[GNC] Thornefamilytrust & DavidC answer

[David Carlson]

It is probable that the nightly build <
https://code.gnucash.org/builds/win32/maint/gnucash-3.0-2018-04-23-git-3.0-87-g14c30344c+.setup.exe>
(or newer, already) of of GnuCash is substantially improved over the
official 3.0 release, but it is not an official release that has undergone
all of the testing (both automatic and human) of an official release.  It
may or may not still be missing the fix for your specific problem.

I would like to add that the jump to release 3.0 is a giant step forward
that involves not only many improvements but also many changes required by
the fact that some of the code that GnuCash used in the earlier days is no
longer supported by its developers or other programmers.

It was impossible to predict all of the ways that GnuCash is installed and
used around the world and it turned out that the 3.0 release had some
flaws, which the developers are addressing.  They do not want to knowingly
release another edition with any of the known show-stopper flaws,
especially when there is an option for users to revert to the previous
release which is working fine, albeit missing a lot of nice improvements.

Give them time to solve the bugs and produce a fine, highly polished
package.

David C

On Tue, Apr 24, 2018 at 7:26 AM, bbaruu <bbaruu at gmail.com> wrote:

> Please, not so snippy sport!   I reverted to v2 GNC as well, then
> reinstalled v3 which process asked to uninstall v2 -- after which v3 works
> just fine.  No other change I know of.  A little more thought there.  Just
> sayin'
>
>
> Sent from my Samsung Galaxy smartphone.
> _______________________________________________
> 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
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -----
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.