Re: Frameworks / Plasma/ Gear Release Schedule Plan
Am Dienstag, 12. September 2023, 21:42:37 CEST schrieb christ...@cullmann.io: > Hi, > > i prepared some merge request for the switch in the meta data: > > https://invent.kde.org/sysadmin/repo-metadata/-/merge_requests/185 > > A question about the CMake changes: > > Is there some preferred way to switch? > > I would just alter the defaults to > > set(QT_REQUIRED_VERSION "6.4.0") > set(QT_MAJOR_VERSION "6") > set(KF_MIN_VERSION "5.240.0") > set(KF_MAJOR_VERSION "6") > > in the first step and start later to remove the version ifs. For Gear the minimum versions are changed by the individual projects, last time I looked there was also no consistent naming of these CMake variables, not have a 'KF_MAJOR_VERSION' variable at all. (Actually I never seen a KF_MAJOR_VERSION variable before, so maybe only Kate?). For reference Frameworks right now requires at least Qt 6.5. I think explicitely setting QT_MAJOR_VERSION to 6 is not needed, including ECM with 5.240 will enable using Qt 6 install paths. (Of course it doesn't hurt to be explicit) > Greetings > Christoph David
Re: Frameworks / Plasma/ Gear Release Schedule Plan
Hi, i prepared some merge request for the switch in the meta data: https://invent.kde.org/sysadmin/repo-metadata/-/merge_requests/185 A question about the CMake changes: Is there some preferred way to switch? I would just alter the defaults to set(QT_REQUIRED_VERSION "6.4.0") set(QT_MAJOR_VERSION "6") set(KF_MIN_VERSION "5.240.0") set(KF_MAJOR_VERSION "6") in the first step and start later to remove the version ifs. Greetings Christoph
Re: Frameworks / Plasma/ Gear Release Schedule Plan
El diumenge, 10 de setembre de 2023, a les 19:50:48 (CEST),
christ...@cullmann.io va escriure:
> On 2023-09-09 13:57, Luigi Toscano wrote:
> Hi,
>
> yes, good point.
>
> Just a technical question: if we do this after that period, what is
> the process to do it for an application belonging to Gear?
>
> Will it just be sufficient e.g. for Kate to drop the Qt 5 variants
> in
>
> https://invent.kde.org/utilities/kate/-/blob/master/.kde-ci.yml?ref_typ
> e=hea ds
>
> and
>
> https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_
> type= heads
>
> and require KF 6 + Qt 6 in the CMake files or is there additional
> stuff
> that
> needs updates to avoids one breaks stuff?
> >>>
> >>> My guess is what you are describing plus updating things in
> >>> repo-metadata, i
> >>> can think of
> >>>
> >>> dependencies/logical-module-structure
> >>> to update the branch info (i.e. kf5-qt5 won't be master anymore, i
> >>> guess
> >>> point it to the latest stable branch)
> >>>
> >>> dependencies/dependency-data-kf6-qt6
> >>> to update the dependency info
> >>> But this is autogenerated by Nico scripts nowadays so... maybe not?
> >>> or prod
> >>> him to run the script?
> >>>
> >>> projects/*/*/i18n.json
> >>> to update the i18n branch information
> >>>
> >>> Anything else I am missing?
> >>
> >> Hi,
> >>
> >> Thanks for the additional pointers.
> >>
> >> Given no one did seem to oppose so far, I would consider to switch
> >> Kate to Qt
> >> 6 in master next Wednesday and start the bit Qt 6 run :)
> >
> > When you switch a branch to qt6, please remember to ping the
> > translation team
> > because we need to move the translations. Probably the best way is to
> > mention
> > the translation team in the merge request to sysadmin/repo-metadata.git
> > which
> > updates the content of the i18n.json file.
>
> Thanks for the hint.
>
> Just to be sure, perhaps I missed the docs, what would be needed in
>
> https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/projects-invent/
> utilities/kate/i18n.json?ref_type=heads
>
> Now we have:
>
> {"trunk": "none", "stable": "none", "stable_kf5": "release/23.08",
> "trunk_kf5": "master"}
>
> Would it be something like:
>
> {"trunk": "master", "stable": "none", "stable_kf5": "release/23.08",
> "trunk_kf5": "none"}
No.
trunk and master are kde4.
You want trunk_kf6
Cheers,
Albert
>
> Greetings
> Christoph
Re: Frameworks / Plasma/ Gear Release Schedule Plan
On 2023-09-09 13:57, Luigi Toscano wrote:
Hi,
yes, good point.
Just a technical question: if we do this after that period, what is
the process to do it for an application belonging to Gear?
Will it just be sufficient e.g. for Kate to drop the Qt 5 variants
in
https://invent.kde.org/utilities/kate/-/blob/master/.kde-ci.yml?ref_type=hea
ds
and
https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type=
heads
and require KF 6 + Qt 6 in the CMake files or is there additional
stuff
that
needs updates to avoids one breaks stuff?
My guess is what you are describing plus updating things in
repo-metadata, i
can think of
dependencies/logical-module-structure
to update the branch info (i.e. kf5-qt5 won't be master anymore, i
guess
point it to the latest stable branch)
dependencies/dependency-data-kf6-qt6
to update the dependency info
But this is autogenerated by Nico scripts nowadays so... maybe not?
or prod
him to run the script?
projects/*/*/i18n.json
to update the i18n branch information
Anything else I am missing?
Hi,
Thanks for the additional pointers.
Given no one did seem to oppose so far, I would consider to switch
Kate to Qt
6 in master next Wednesday and start the bit Qt 6 run :)
When you switch a branch to qt6, please remember to ping the
translation team
because we need to move the translations. Probably the best way is to
mention
the translation team in the merge request to sysadmin/repo-metadata.git
which
updates the content of the i18n.json file.
Thanks for the hint.
Just to be sure, perhaps I missed the docs, what would be needed in
https://invent.kde.org/sysadmin/repo-metadata/-/blob/master/projects-invent/utilities/kate/i18n.json?ref_type=heads
Now we have:
{"trunk": "none", "stable": "none", "stable_kf5": "release/23.08",
"trunk_kf5": "master"}
Would it be something like:
{"trunk": "master", "stable": "none", "stable_kf5": "release/23.08",
"trunk_kf5": "none"}
Greetings
Christoph
Re: Frameworks / Plasma/ Gear Release Schedule Plan
christ...@cullmann.io ha scritto: > On 2023-09-05 23:08, Albert Astals Cid wrote: >> El dimarts, 5 de setembre de 2023, a les 22:42:13 (CEST), >> christ...@cullmann.io va escriure: >>> On 2023-09-04 22:59, Albert Astals Cid wrote: >>> > El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David >>> > Edmundson va >>> > >>> > escriure: >>> >> Following on from the last Akademy we checked where we were with our >>> >> development progress in a meeting and settled on the following plan >>> >> >>> >> for all 3 major parts: >>> >> - In KDE Gear master will be open for Qt6 code to land for those >>> >> >>> >> ready to move. Not all apps need to port. >>> > >>> > For the trigger happy among us... >>> > >>> > This is a plan/proposal, let's give people at least one week to >>> > comment/ >>> > disagree on it before making master Qt6-only for Gear apps. >>> >>> Hi, >>> >>> yes, good point. >>> >>> Just a technical question: if we do this after that period, what is >>> the process to do it for an application belonging to Gear? >>> >>> Will it just be sufficient e.g. for Kate to drop the Qt 5 variants in >>> >>> https://invent.kde.org/utilities/kate/-/blob/master/.kde-ci.yml?ref_type=hea >>> ds >>> >>> and >>> >>> https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type= >>> heads >>> >>> and require KF 6 + Qt 6 in the CMake files or is there additional stuff >>> that >>> needs updates to avoids one breaks stuff? >> >> My guess is what you are describing plus updating things in repo-metadata, i >> can think of >> >> dependencies/logical-module-structure >> to update the branch info (i.e. kf5-qt5 won't be master anymore, i guess >> point it to the latest stable branch) >> >> dependencies/dependency-data-kf6-qt6 >> to update the dependency info >> But this is autogenerated by Nico scripts nowadays so... maybe not? or prod >> him to run the script? >> >> projects/*/*/i18n.json >> to update the i18n branch information >> >> Anything else I am missing? > > Hi, > > Thanks for the additional pointers. > > Given no one did seem to oppose so far, I would consider to switch Kate to Qt > 6 in master next Wednesday and start the bit Qt 6 run :) When you switch a branch to qt6, please remember to ping the translation team because we need to move the translations. Probably the best way is to mention the translation team in the merge request to sysadmin/repo-metadata.git which updates the content of the i18n.json file. Ciao -- Luigi
Re: Frameworks / Plasma/ Gear Release Schedule Plan
On 2023-09-05 23:08, Albert Astals Cid wrote: El dimarts, 5 de setembre de 2023, a les 22:42:13 (CEST), christ...@cullmann.io va escriure: On 2023-09-04 22:59, Albert Astals Cid wrote: > El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David > Edmundson va > > escriure: >> Following on from the last Akademy we checked where we were with our >> development progress in a meeting and settled on the following plan >> >> for all 3 major parts: >> - In KDE Gear master will be open for Qt6 code to land for those >> >> ready to move. Not all apps need to port. > > For the trigger happy among us... > > This is a plan/proposal, let's give people at least one week to > comment/ > disagree on it before making master Qt6-only for Gear apps. Hi, yes, good point. Just a technical question: if we do this after that period, what is the process to do it for an application belonging to Gear? Will it just be sufficient e.g. for Kate to drop the Qt 5 variants in https://invent.kde.org/utilities/kate/-/blob/master/.kde-ci.yml?ref_type=hea ds and https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type= heads and require KF 6 + Qt 6 in the CMake files or is there additional stuff that needs updates to avoids one breaks stuff? My guess is what you are describing plus updating things in repo-metadata, i can think of dependencies/logical-module-structure to update the branch info (i.e. kf5-qt5 won't be master anymore, i guess point it to the latest stable branch) dependencies/dependency-data-kf6-qt6 to update the dependency info But this is autogenerated by Nico scripts nowadays so... maybe not? or prod him to run the script? projects/*/*/i18n.json to update the i18n branch information Anything else I am missing? Hi, Thanks for the additional pointers. Given no one did seem to oppose so far, I would consider to switch Kate to Qt 6 in master next Wednesday and start the bit Qt 6 run :) (If nothing comes up here) The everybody had a week to chime in. Let's make our Qt 6 based 'bundled' release next year a good one ;) Greetings Christoph Cheers, Albert Greetings Christoph >> - The KDE Gear release will move by 2 months to allow for the extra >> >> time needed for testing initial Qt6 changes >> >> - An Alpha will be made in November (a soft freeze in Plasma terms) >> >> - Betas/RCs will be made throughout December and January (3 releases, >> >> 3 weeks apart) >> >> - Final release of all 3 major parts in sync in February >> >> Due to the delay of KDE Gear by an additional patch release of 23.08 >> will be made. > > Or maybe even two if there's bugfixes flowing. > > Cheers, > > Albert >> >> David Edmundson
Re: Frameworks / Plasma/ Gear Release Schedule Plan
El dimarts, 5 de setembre de 2023, a les 22:42:13 (CEST), christ...@cullmann.io va escriure: > On 2023-09-04 22:59, Albert Astals Cid wrote: > > El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David > > Edmundson va > > > > escriure: > >> Following on from the last Akademy we checked where we were with our > >> development progress in a meeting and settled on the following plan > >> > >> for all 3 major parts: > >> - In KDE Gear master will be open for Qt6 code to land for those > >> > >> ready to move. Not all apps need to port. > > > > For the trigger happy among us... > > > > This is a plan/proposal, let's give people at least one week to > > comment/ > > disagree on it before making master Qt6-only for Gear apps. > > Hi, > > yes, good point. > > Just a technical question: if we do this after that period, what is > the process to do it for an application belonging to Gear? > > Will it just be sufficient e.g. for Kate to drop the Qt 5 variants in > > https://invent.kde.org/utilities/kate/-/blob/master/.kde-ci.yml?ref_type=hea > ds > > and > > https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type= > heads > > and require KF 6 + Qt 6 in the CMake files or is there additional stuff > that > needs updates to avoids one breaks stuff? My guess is what you are describing plus updating things in repo-metadata, i can think of dependencies/logical-module-structure to update the branch info (i.e. kf5-qt5 won't be master anymore, i guess point it to the latest stable branch) dependencies/dependency-data-kf6-qt6 to update the dependency info But this is autogenerated by Nico scripts nowadays so... maybe not? or prod him to run the script? projects/*/*/i18n.json to update the i18n branch information Anything else I am missing? Cheers, Albert > > Greetings > Christoph > > >> - The KDE Gear release will move by 2 months to allow for the extra > >> > >> time needed for testing initial Qt6 changes > >> > >> - An Alpha will be made in November (a soft freeze in Plasma terms) > >> > >> - Betas/RCs will be made throughout December and January (3 releases, > >> > >> 3 weeks apart) > >> > >> - Final release of all 3 major parts in sync in February > >> > >> Due to the delay of KDE Gear by an additional patch release of 23.08 > >> will be made. > > > > Or maybe even two if there's bugfixes flowing. > > > > Cheers, > > > > Albert > >> > >> David Edmundson
Re: Frameworks / Plasma/ Gear Release Schedule Plan
On 2023-09-04 22:59, Albert Astals Cid wrote: El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David Edmundson va escriure: Following on from the last Akademy we checked where we were with our development progress in a meeting and settled on the following plan for all 3 major parts: - In KDE Gear master will be open for Qt6 code to land for those ready to move. Not all apps need to port. For the trigger happy among us... This is a plan/proposal, let's give people at least one week to comment/ disagree on it before making master Qt6-only for Gear apps. Hi, yes, good point. Just a technical question: if we do this after that period, what is the process to do it for an application belonging to Gear? Will it just be sufficient e.g. for Kate to drop the Qt 5 variants in https://invent.kde.org/utilities/kate/-/blob/master/.kde-ci.yml?ref_type=heads and https://invent.kde.org/utilities/kate/-/blob/master/.gitlab-ci.yml?ref_type=heads and require KF 6 + Qt 6 in the CMake files or is there additional stuff that needs updates to avoids one breaks stuff? Greetings Christoph - The KDE Gear release will move by 2 months to allow for the extra time needed for testing initial Qt6 changes - An Alpha will be made in November (a soft freeze in Plasma terms) - Betas/RCs will be made throughout December and January (3 releases, 3 weeks apart) - Final release of all 3 major parts in sync in February Due to the delay of KDE Gear by an additional patch release of 23.08 will be made. Or maybe even two if there's bugfixes flowing. Cheers, Albert David Edmundson
Re: Frameworks / Plasma/ Gear Release Schedule Plan
El dilluns, 4 de setembre de 2023, a les 18:50:45 (CEST), David Edmundson va escriure: > Following on from the last Akademy we checked where we were with our > development progress in a meeting and settled on the following plan > for all 3 major parts: > > - In KDE Gear master will be open for Qt6 code to land for those > ready to move. Not all apps need to port. For the trigger happy among us... This is a plan/proposal, let's give people at least one week to comment/ disagree on it before making master Qt6-only for Gear apps. > > - The KDE Gear release will move by 2 months to allow for the extra > time needed for testing initial Qt6 changes > > - An Alpha will be made in November (a soft freeze in Plasma terms) > > - Betas/RCs will be made throughout December and January (3 releases, > 3 weeks apart) > > - Final release of all 3 major parts in sync in February > > Due to the delay of KDE Gear by an additional patch release of 23.08 > will be made. Or maybe even two if there's bugfixes flowing. Cheers, Albert > > David Edmundson
Frameworks / Plasma/ Gear Release Schedule Plan
Following on from the last Akademy we checked where we were with our development progress in a meeting and settled on the following plan for all 3 major parts: - In KDE Gear master will be open for Qt6 code to land for those ready to move. Not all apps need to port. - The KDE Gear release will move by 2 months to allow for the extra time needed for testing initial Qt6 changes - An Alpha will be made in November (a soft freeze in Plasma terms) - Betas/RCs will be made throughout December and January (3 releases, 3 weeks apart) - Final release of all 3 major parts in sync in February Due to the delay of KDE Gear by an additional patch release of 23.08 will be made. David Edmundson
