[GNC] Concern with the lengthy list of "Known Issues"

[Christopher Lam]

I think the UI upgrades have been an unfortunate but necessary consequence
of many Linux distributions deciding to kill GTK2 and all GTK2- based apps.
If jralls or gjanssens haven't spent countless hours upgrading components
then GnuCash would have been dropped from all major distributions.

Most UI issues *can* be tweaked via CSS -- as everything here is
opensource, users are encouraged to dive in and amend to their liking.

Finally the list of issues bein long; apart from the GTK3 preferences  I
believe most of the "new" known issues in 3.x were also present, but
undocumented in 2.x.

On Mon, 22 Jul 2019 at 20:10, Christoph R <subscriptions+listen at rohland.net>
wrote:

> Hi,
>
> I am using gnucash since 2004 for multiple accounts and have my whole
> personal history since then in one file. I am running gnucash on MacOs in
> German which is somewhat special and the only dev for MacOs is John. Thanks
> to him for all the work putting he is putting in! I was a pretty happy user
> up until 3.0.
>
> But with the 3.x series there are more problems than I am used to and
> progress is very slow. The only version working for me so far is 3.5, which
> is my production version for now. Versions before crashed or failed on
> important operations (like the csv importer, which is the main reason I am
> using 3.x). 3.6 apparently has a stray ifdef on MacOs which makes the
> program always fall back to English. So I am back to 3.5.
>
> And the release cycle is pretty long. So even when bugs are fixed it takes
> a lot of time to get them in a stable build.
>
> As much as I am proponent of using the latest software versions: with
> gnucash 3.x I cannot wholeheartedly
> recommend it. The good thing though is that you can try and go back. The
> latest 2.x version reads 3.x files. And switching between 3.x versions back
> and forth works too.
>
> Cheers,
> Christoph
>
> > Am 21.07.2019 um 19:31 schrieb scotts <ssoderling at shaw.ca>:
> >
> > I have been using Gnucash for about 3 years now, and for the most part
> > enjoying the experience! I use it for my personal finances (bank
> accounts,
> > credit cards, investments, etc). I am also the treasurer of a golf club
> > association and am considering moving their accounting over to Gnucash.
> >
> > I am currently using Windows version 2.6.21. Of course at the moment, the
> > most current stable release is version 3.6. My only hesitation in
> upgrading
> > is what seems to me to be a very long list of "known issues" with the
> > release.
> >
> > I'm looking for other opinions. In my experience, version 2.6.21 seems to
> > pretty much work as advertised. No crashes, runs quickly enough on my
> > computer, all the functions I've tried seem to work fine. Normally I
> would
> > upgrade any software to the latest release, hopefully taking advantage of
> > bug fixes and new features. But when I see the long list of issues, I
> > hesitate.
> >
> > Would appreciate any comments from others. Am I being overly paranoid?
> > Thanks a lot!
> >
> >
> >
> > --
> > Sent from:
> http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> > _______________________________________________
> > 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.
>
> _______________________________________________
> 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.
>