Hi, Just want to summarize the QtSql Session at QtCS 2012.
To be very honest, QtSql contributors were not well-represented at the summit in Berlin. Nevertheless, I was able to speak with some of the original developers of QtSql, who are now doing other things mostly, and exchanged some ideas. QtSql will mostly likely be moved into its own module. The main reason for this is the efficiency of CI testing. It only makes sense to run the sql tests when something has been changed in the module. At the moment, the tests are only run on sqlite, but if more drivers are tested, this will become an even larger consideration. The fact is that nearly all QtSql development right now depends on community contributions. No organization, as far as I know, is sponsoring new work. As the maintainer, one of my responsibilities is to keep on top of the bugs filed for QtSql. One of the subjects discussed at the summit was how to manage bugs and feature requests without any resources to assign. We're forced to make pretty liberal use of "rejected: out of scope, patches welcome". It's much easier to ask volunteers to review proposed changes than it is to ask them to solve bugs and implement requested features from scratch. It doesn't make sense to have open feature requests hanging around for years when nobody is working on them. Of course, we'll still do what we can to fix show stoppers. There have been important community contributions to QtSql, but more are welcome. I hope those interested in QtSql will take a look at the changes already made in Qt 5, take advantage of them, and be inspired to contribute. Please feel free to respond with comments and questions. regards, Mark _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
