Next release 2.4.1? Branching stable and trunk sooner or later?

[Phil Longstaff]

On Thu, 2011-02-03 at 16:39 -0800, John Ralls wrote:
> On Jan 30, 2011, at 10:28 AM, Geert Janssens wrote:
> 
> > On Sunday 30 January 2011, John Ralls wrote:
> >> On Jan 29, 2011, at 4:15 PM, Phil Longstaff wrote:
> >>> On Thu, 2011-01-27 at 17:21 -0500, Phil Longstaff wrote:
> >>>> On Thu, 2011-01-27 at 23:01 +0100, Geert Janssens wrote:
> >>>>>> I seem to have some issues with the table versioning that was added
> >>>>>> recently. I have an sqlite3 based book and whenever I open it, GnuCash
> >>>>>> tells me it's created with an old version and should be upgraded. If I
> >>>>>> click ok, the file is being re-saved, but the next time I open the
> >>>>>> file, it asks me the same question again.
> >>>>>> 
> >>>>>> I have this with a testfile (from the 2.3.x days) with just one
> >>>>>> transaction in it.
> >>>>>> 
> >>>>>> Geert
> >>>>> 
> >>>>> Hmm, it even happens with a completely new file, with only accounts in
> >>>>> it (no transactions added yet).
> >>>> 
> >>>> I'll hold off on 2.4.1 until this is fixed.
> >>> 
> >>> I haven't followed checkins closely enough.  Is 2.4.1 ready to go?  Let
> >>> me know when it is.
> >> 
> >> I've fixed Geert's problem, I think.
> > Indeed, this issue is fixed. The new versioning code works nicely. Thanks.
> > 
> >> But Christoph Holtermann has found a
> >> problem with invoice loading [1]
> > I hit this issue as well. Until now I had ignored it as I thought is was a 
> > side-effect of other problems (like having the sqlite3 file on a cifs mounted 
> > share), but I saw it now as well with a file stored on nfs, which never caused 
> > issues before.
> > I just looked at Christoph's path now (from bug 640061 [1]). It looks good in 
> > concept, though I'd move the two changes to different places in the code. I'm 
> > now running a test build to see if it works ok.
> 
> Phil,
> 
> Are you waiting for something else to tag & release 2.4.1? Geert closed 640061 on Sunday.

Just waiting for the go-ahead.