Re: ANNOUNCE: GnuCash 2.1.4 Released
Windows packages are now available. Since this is a release candidate, please test any and all features that you use. On 6/16/07, Chris Lyttle [EMAIL PROTECTED] wrote: GnuCash 2.1.4 released The GnuCash development team proudly announces GnuCash 2.1.4 aka Release Candidate 1, the first release candidate for the upcoming 2.2.0 stable release of the GnuCash Open Source Accounting Software. With this new release series, GnuCash is available on Microsoft Windows for the first time, and it also runs on GNU/Linux, *BSD, Solaris and Mac OSX. This release is intended for developers and testers who want to help tracking down all those bugs that are still in there. ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: GnuCash 2.1.4 Released
Hi, I have 0,02 NOK input on this. I have been using the unstable version for a while now, and because of a recent but unrelated problem went back to 2.0.5. That version refused to open the file with an error message approximately like unable to parse the XML. I went back to 2.1.4, checked scheduled transactions and noted one completed fire once transaction. I deleted that entry and saved. Now 2.0.5 opens the file without problems. So the incompatibility is quite minor. Reiterating on things previously said: In version 2.1.2 the format for scheduled transactions 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 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 with (possibly completed) scheduled transactions, then these files will not be readable by older versions. Therefore, if you use or have used scheduled transactions, you are advised to make a backup copy of the data file before saving it with the new GnuCash. If you must, you can make an existing data file readable by older versions of GnuCash by deleting all records of scheduled transactions in the scheduled transactions editor. Bye, Bastiaan. Christian Stimming wrote: 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 ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
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
Re: GnuCash 2.1.4 Released
*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. I could interpret this in two ways: If you have an old data file, the new Gnucash will be unable to read it, and worse, might destroy it. This is a disaster, if true. 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. I would describe both of these by saying that it is not backward compatible. Can you clarify which it is? 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
Re: Re: GnuCash 2.1.4 Released
On Sat, Jun 16, 2007 at 02:06:53PM -0700, Thomas Bushnell BSG wrote: *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. I could interpret this in two ways: If you have an old data file, the new Gnucash will be unable to read it, and worse, might destroy it. This is a disaster, if true. 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. I would describe both of these by saying that it is not backward compatible. Can you clarify which it is? It's the second of those two interpretations. And it's only a problem for people using scheduled transactions. --Beth Beth Leonard http://www.LeonardFamilyVideos.com ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: Re: GnuCash 2.1.4 Released
It's the second of those two interpretations. And it's only a problem for people using scheduled transactions. Ok, then next question. What exactly happens if a user tries to load a new-format file into an old gnucash? 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
Re: GnuCash 2.1.4 Released
Thomas Bushnell BSG [EMAIL PROTECTED] writes: It's the second of those two interpretations. And it's only a problem for people using scheduled transactions. Ok, then next question. What exactly happens if a user tries to load a new-format file into an old gnucash? It will generically complain that the file is unreadable; I forget the exact error message text. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED] pgpIu9YGNjgLg.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
On Sat, 2007-06-16 at 20:05 -0400, Josh Sled wrote: Thomas Bushnell BSG [EMAIL PROTECTED] writes: It's the second of those two interpretations. And it's only a problem for people using scheduled transactions. Ok, then next question. What exactly happens if a user tries to load a new-format file into an old gnucash? It will generically complain that the file is unreadable; I forget the exact error message text. 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. 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
