QtCS2021 - Moving to qt6.git: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(Created page with "Category: QtCS2021 ==Summary== Wrap up the mailing list discussion from https://lists.qt-project.org/pipermail/development/2021-January/040855.html and QTQAINFRA-4200 =...")
 
 
(One intermediate revision by the same user not shown)
Line 3: Line 3:
==Summary==
==Summary==


Wrap up the mailing list discussion from https://lists.qt-project.org/pipermail/development/2021-January/040855.html and QTQAINFRA-4200
Wrap up the mailing list discussion from https://lists.qt-project.org/pipermail/development/2021-January/040855.html and [https://bugreports.qt.io/browse/QTQAINFRA-4200 QTQAINFRA-4200]


==Session Owners:==
==Session Owners:==


* Volker Hilsheimer (volker.hilsheimer@qt.io)
*Volker Hilsheimer (volker.hilsheimer@qt.io)


==Notes==
==Notes==
* We need a CI task force that continuously looks at the experience of the developers contributing to/working on Qt
* Rename qt5.git to qt.git (keep an alias, remove after some long enough period)
** qt.git renamed to qt4.git
** branches to manage Qt 5 vs Qt 6 (vs Qt 7...)
* There is a usecase for a supermodule that provides a stable Qt distribution
** baseline for packaging
** linux distros
** casual contributors
* There is a usecase for a subset of submodules that is consistent with each other, but ignores other downstream modules
** regular contributors
* Structural changes to the submodules
** Proposal: Examples in separate repository
** QtNetwork : moving it out of qtbase requires some management of the private dependencies
** QtQuickControls 2 should move into qtdeclarative
* Modules that would benefit from working against multiple versions of Qt and/or have their own release cycle
** QtWebEngine
** Qt3D

Latest revision as of 14:00, 22 June 2021


Summary

Wrap up the mailing list discussion from https://lists.qt-project.org/pipermail/development/2021-January/040855.html and QTQAINFRA-4200

Session Owners:

  • Volker Hilsheimer (volker.hilsheimer@qt.io)

Notes

  • We need a CI task force that continuously looks at the experience of the developers contributing to/working on Qt
  • Rename qt5.git to qt.git (keep an alias, remove after some long enough period)
    • qt.git renamed to qt4.git
    • branches to manage Qt 5 vs Qt 6 (vs Qt 7...)
  • There is a usecase for a supermodule that provides a stable Qt distribution
    • baseline for packaging
    • linux distros
    • casual contributors
  • There is a usecase for a subset of submodules that is consistent with each other, but ignores other downstream modules
    • regular contributors
  • Structural changes to the submodules
    • Proposal: Examples in separate repository
    • QtNetwork : moving it out of qtbase requires some management of the private dependencies
    • QtQuickControls 2 should move into qtdeclarative
  • Modules that would benefit from working against multiple versions of Qt and/or have their own release cycle
    • QtWebEngine
    • Qt3D