Hi, I agree that it would be nice to properly separate Solutions (to enforce their reusability, and to make it easier to include the module into other projects).
I'm also convinced that Jarek would do a good job as the maintainer of the module. I have however two questions: 1. How this will affect packaging/releasing of QtCreator? 2. Will the release cycle of the modle be coupled to Creator's release cycle? Fabian ________________________________________ Von: Development <development-boun...@qt-project.org> im Auftrag von apoenitz <apoen...@t-online.de> Gesendet: Donnerstag, 30. November 2023 19:39 An: development@qt-project.org Betreff: [Development] Proposing new Qt Creator module: Qt Creator Solutions Hi all. As you may know, we've started to separate parts of code originally created specifically for Qt Creator from other parts of Creator's infrastructure in order to make them more easily reusable in other projects or possible become a proper Qt module at some time. These "Solutions" are currently collected in a subdirectory[1] of the main Qt Creator repo but could be split out further in the future if needed. I propose to make this setup an official Module of Qt Creator, and herewith also nominate Jarek as Maintainer. Jarek has been pushing the idea and is the author of the biggest existing Qt Creator Solution: TaskTree[2], so for me this is the obvious choice. Comments/questions/opinions? Andre' [1] https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/libs/solutions [2] https://wiki.qt.io/TaskTree -- 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
