Liz, A good point. It’s already a bit fuzzy because we’ve been slipstreaming features since 3.x, guarding them with flags that warn when a user tries to open a file that uses a newer feature that isn’t available in the older version of GnuCash that their trying to use. Of course there are also changes that while they affect what GnuCash can do they don’t change what is stored. Importer changes are a good example: We enabled all of AQBanking’s import modules in 5.0, greatly expanding the formats that GnuCash can import. That has no effect on what gets written into the data file. Ditto for the vastly improved CSV importer introduced in 4.0.
Regards, John Ralls > On Mar 30, 2025, at 19:34, ed...@billiau.net wrote: > > On Sun, 30 Mar 2025 22:12:00 -0400 > Brian Rater <blrn...@gmail.com> wrote: > >> We still have some major things in the pipeline that would warrant a >> major release, it's just that noone has had available time to work >> them. I am still planning to rewrite qif import and should have time >> to work on this now that I am retired. I am still hoping to finish >> it this year and then I'm planning to look into a major replacement >> of reports, which will likely take a couple of years. Perhaps we >> continue with minor number revisions until we have something major. > > > Just a thought that advice is often given to people wanting to upgrade > from an old version that they need to go to the last release of each > version number in turn. > Changes in the numbering would make that advice unworkable as a simple > answer, and we'd need a little table of which versions to go to for a > long overdue upgrade. > > > Liz > _______________________________________________ > 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
