[GNC-dev] Request of keeping a 2.6 branch still alive (Re: branch-2.6)

[John Ralls]

> On 10. Jun 2018, at 13:41, Christian Stimming <christian at cstimming.de> wrote:
> 
> Am Samstag, 2. Juni 2018, 17:28:27 schrieb John Ralls:
>>> there is already a private fork, just as everyone else
>>> around here is free to privately fork anything that he/she wants.
>>> https://github.com/cstim/gnucash/tree/branch-2.6
>> 
>> BTW, there's already a 2.6.21 because the MySQL backend was broken on
>> 2.6.20. It was released April 10.
> 
> Dear John,
> 
> yes I confused the numbers here. There was a 2.6.21 in April. I would happily 
> switch to the 3.0 branch (git-maint) on my system, as soon as I see for myself 
> that it is up and running on my (still old) ubuntu 14.04 system.
> 
> However, after I eventually was able to build and run the newer branch [1], it 
> turns out to crash in the register on every normal usage. Of course I've filed 
> a bug on that one [2] (with gtk-3.10.8 that is), and I will continue looking 
> into resolving this problem myself, too. However, until we are able to resolve 
> this problem, my guess is that on ubuntu 14.04, there is no 3.0.x version that 
> is usable. Can someone report otherwise? If yes, I would happily discuss in 
> detail the steps that I'm missing.
> 
> Until then, I would again propose to keep a 2.6 branch alive for a few more 
> months, so that a potential 2.6.22 release with minor bugfixes might be 
> released as well for systems on the age of ubuntu 14.04.
> 
> Best Regards,
> 
> Christian
> 
> [1] For several days, I was stuck at the error at start-up "Undefined 
> variable: gnc-build-userdata-path" that got reported also by e.g. Herbert 
> Thoma here. For future reference: The solution was to remove any instance of 
> an old (2.6) gnucash from the library path both at build time and at run time.
> 
> [2] https://bugzilla.gnome.org/show_bug.cgi?id=796556
> 

Christian,

Your crash appears to be a dupe of a Gtk bug, details and a possible work-around on your bug report.

You seem to have missed out that we've changed the version system, there's no 3.0.x at all. There was 3.0, the current release is 3.1, and the next one will be 3.2.

I'm not interested in continually re-arguing further 2.6.x releases.

Regards,
John Ralls