Re: GnuCash 2.1.4 Released
Thomas Bushnell BSG [EMAIL PROTECTED] writes: Ah, good. Thanks for indulging me. This all sounds like it's exactly the best one can expect, given the necessity of changing the format in the first place. It could be better ... 1.8/2.0 could (non-)silently ignore XML sub-trees that they did not understand. Then, 2.2 could emit both the old (FreqSpec) and new (Recurrence) structures and the files would be backward-compatible. Of course, it'd be custom, new code to generate a FreqSpec from a Recurrence, and there are features of the Recurrence that can't be expressed in a FreqSpec, but only if used could 2.2 refuse to save in pre-2.2 format. Unfortunately, our XML error handling sucks. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] pgpisPqizQuHN.pgp Description: PGP signature ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: GnuCash 2.1.4 Released
Am Samstag, 16. Juni 2007 23:06 schrieb Thomas Bushnell BSG: *DATA FILE NOTICE* If you are using Scheduled Transactions, the data file saved by GnuCash 2.1.2 and higher is *NOT* backward-compatible with GnuCash 2.0 anymore. Please make a safe backup of your 2.0 data before upgrading to 2.1.2. This kind of announcement is extremely problematic from a redistributor/packager perspective (mine). But maybe it's just the announcement that's problematic and not the actual change it points to. As already written in earlier responses, the meaning should have been as follows: If you save a data file with the new Gnucash, then an old Gnucash will be unable to read it. If this is true, then it means that users who start using the new Gnucash will have committed to the new one, essentially, for that file, and backups are advised in case going back to the old Gnucash is needed. Do you have any suggestions to improve the wording in our announcements in order to avoid further problems with ambiguous message? That would be very helpful. Christian ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: GnuCash 2.1.4 Released
On Sun, 2007-06-17 at 15:44 +0200, Christian Stimming wrote: Do you have any suggestions to improve the wording in our announcements in order to avoid further problems with ambiguous message? That would be very helpful. Spell out in excruciating detail the different circumstances and exactly what a user can expect to happen, and don't use words like backward compatible that admit of too many different meanings. So I think in this case, something like: In version XXX the format for YYY in data files was changed. Files using the old format will be read without problems by new versions, but the new version of gnucash only writes the new format. The new format cannot be properly loaded by older versions of Gnucash. (If you try, the file will fail to be loaded with an error message.) As a result, if you begin using the new Gnucash, and you have data files using feature YYY, then the files you save will not be readible by older versions. ... (more must be said, this is just the beginning!) Thomas signature.asc Description: This is a digitally signed message part ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
