Hi, as an addendum to what Volker said, (parts of) the official process are outlined in https://contribute.qt-project.org/quips/14. Given the history, there's obviously no need to add it to playground first, and the aim should be to move it into the Qt framework (whether as TP or as a full-fledged module).
Now we are already past 6.10 module and platform freeze, so the earliest target is 6.11. We should obviously start the process for this as soon as possible, so that it won't slip. Though mind that many potential reviewer might currently be a bit busy with 6.10 feature freeze and the following header-review. For TaskTree, the question should be whether it ought to be in qtbase. Unless we see a compelling use case inside another qtbase module, I'd recommend adding it in a separate repository. Then it can still be used in other Qt modules, but you're much less likely to compete with other tasks for CI integrations. In the meantime, you can of course use the existing qtbase commit to demonstrate that the checklist from https://contribute.qt-project.org/quips/14#entering-technical-preview is handled (tests, documentation and code style don't depend on it). From a quick glance at the commit, there are at least a few things that could be done while the repo discussio is ongoing (using CMake generated include guards, removing references to Creator from the docs, class documentation for some classes currently missing – but I should put that on gerrit). If we decide to go with a separate repository, I'm sure Dennis and Alexey can share of the things they've learned from QtGRPC. Kind regards, Fabian ________________________________________ Von: Development <development-boun...@qt-project.org> im Auftrag von Jaroslaw Kobus via Development <development@qt-project.org> Gesendet: Montag, 26. Mai 2025 15:56 An: development@qt-project.org Betreff: [Development] Making TaskTree a public API Hi All, I'd like to start a broader discussion about including TaskTree in Qt and making it a public API. TaskTree is a solution broadly used in QtCreator in hundreds of places, for convenient managing of sets of asynchronous tasks of various types, including running processes, functions in separate threads, network communication, and much more. The solution is easily extensible in terms of new task types. It's a matured solution, with a 2.5 years of lifetime already. TaskTree is already a part of Qt, but used just in one place, and privately so far (qtbase/src/assets/downloader). The main page for the TaskTree is here: https://wiki.qt.io/TaskTree According to https://bugreports.qt.io/browse/QTBUG-131142 I stared a work that introduces a new Tasking module in qtbase (qtbase/src/tasking). The patch is here: https://codereview.qt-project.org/c/qt/qtbase/+/645458 I'm not sure what is the official process of adding new module to qtbase, thus I'm posting it here, counting for more feedback and a possible agreement for this new module to be a part of Qt. I would be very glad for any further comments and opinions on this topic. All reviews of the mentioned patch are of course very welcome and appreciated. Thanks in advance and best regards, Jarek -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development -- Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
