On Wed, 2009-12-30 at 14:00 -0500, Phil Longstaff wrote: > As far as major pieces for 2.4, the last thing is webkit on windows > (webkit on linux/mac seem to work fine, webkit on windows has some > really bad bugs - fonts unreadable if you print a report). I'm working > on that now, and hope soon to either have a fix or else we'll need to > pull webkit out on windows and go back to gtkhtml. > > 2.4 will support SQL to an sqlite3 db file, or a local or remote mysql > or postgresql db. I've been using the sqlite3 backend quite > successfully, but don't use all of the features. There are still some > bugs that need to be fixed. Even after they are fixed, the decision is > to stay with the XML backend by default, but allow the user to save into > an SQL file and go from there. Note that gnucash is *not* a database > app, and there is no multi-user capability. > > As far as target date goes... I hope to resolve webkit/windows within > the next 2 weeks - either have a version that allows you to print, or > else go back to gtkhtml on windows. Then, a few releases for string > freeze/translation and fixing critical bugs. Maybe end of April?
Well, it appears as though the latest webkit/win32 build does *not* fix the printing font size issue, so I propose that on win32, we stick with gtkhtml. I will update the schedule on the wiki, but will propose a schedule something like: 2.3.9 (3rd week of January) - String freeze 2.3.10 (3rd week of February) - Major bug fixes 2.3.11, 2.3.12, ... Weeks to follow - major bug fixes/translation issues only Sometime in late February, I am going to need some surgery and will be out of commission for a few weeks (up to 6-8 weeks). Either 2.3.X releases will need to wait with a large gap, or else someone else will need to handle the release process during my absence. Phil _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
