2.1.x and allow_file_incompatability
Christian Stimming
stimming at tuhh.de
Tue May 1 08:27:47 EDT 2007
Am Dienstag, 1. Mai 2007 01:12 schrieb Josh Sled:
> There are two places we use the gconf
> key /apps/gnucash/dev/allow_file_incompatibility:
>
> - Scheduled Transactions (FreqSpec->Recurrence)
> - ROOT Account Group
>
> I propose that we flip the default for these two immediately before the
> 2.1.2 release. Thus, starting with 2.1.2, files would no longer be
> backward compatible.
Can you define again "backward compatible"? Does that mean with your proposed
change, a 2.1.2-saved file cannot be read by 2.0.x as long as 1. it contains
scheduled transactions, and 2. the user doesn't manually set this key the
other way round? Which version would be the earliest gnucash version that can
read the new file?
Also, does that mean we've already agreed that a 2.2.0-saved data file cannot
be read by 2.0.x?
As for my thoughts here: I prefer infinite forward and backward
compatibility :-) but if this cannot happen, then 2.1.2 is okay. I'm still
flipping back and forth between 2.0.x and trunk on my data file, though, but
I know the options that I have.
Christian
More information about the gnucash-devel
mailing list