On Feb 13, 2012, at 1:18 PM, Jeff Kletsky wrote: > Once again, it is the beginning of the year and I'm fighting with GNUCash > budgeting to the point where I need to find a solution that is functional for > me. I'd like to be able to return the work to the community, but I don't have > a good idea of what is planned for major functionality changes in GNUCash in > coming releases. For example, I found an email from John Ralls on 2011/09/26 > that suggested that there was some thought of moving off the C-driven queries > and allowing things to be handled by the back end. > > Is there a wiki page somewhere that suggests what major changes are planned > for upcoming releases? > > Also, at one point, there was a development directive that any changes had to > be backward compatible in that previous versions of GNUCash *must* be able to > read newer versions of the data store without failing. This seems to have > resulted in the use of KVP as a generic extension method, rather than > changing the schema and providing upgrade triggers. Is that still the case?
http://wiki.gnucash.org/wiki/Roadmap http://wiki.gnucash.org/wiki/WishList Subject to limited developer availability and interest. ;-) Any changes in the way query works are dependent upon (in order): * Unit test coverage * GObject normalization (making everything into a proper GObject class) * Making reads and writes fully atomic and wrapped in database transactions * Load XML files into an in-memory SQLite db. Once those steps are complete we can change queries to SQL and go multi-user. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
