On 5September2014, at 21:57, Thiago Macieira <thiago.macie...@intel.com> wrote:
> On Thursday 18 September 2014 21:46:27 Jeremy wrote: >> I don’t see an issue with removing it from Qt 5. Is there a general plan for >> modules that exit from production-ready status? > > Modules that exit from production-ready status need to go through the > deprecation ladder: first Done, then Deprecated (with possibly a > replacement), > and then finally Removed. The package should be made to compile with future > versions of Qt. That's what we did for Qt Script Classic, Qt Assistant ADP, > QHttp, QFtp, etc. > > However, let's be clear: QtJsondb never achieved "production-ready" status. > It > never left "pre-alpha" state and was never released. There's no one using it. > Simply remove the link from qt5.git and leave the repo to rot. > It’s the repo hosted on qt-project.org and clones such as qt.gitorious.org that I’m wondering about. Leaving qtjsondb at its current URL is not what I would expect for something that is not part of the Qt 5 bundle. Do we start a qt-abandoned tree? qtplayground is too optimistic. _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
