[F45 test days] KDE 6.7 #922

Open
opened 2026-07-22 11:16:17 +00:00 by kparal · 21 comments
Owner

We want to test KDE for F45, as is usual in each cycle. It's likely going to be KDE 6.7 (already stable), because 6.8 has a release date after F45.

We want to test KDE for F45, as is usual in each cycle. It's likely going to be KDE 6.7 (already stable), because 6.8 has a release date after F45.
Author
Owner

@jgroman Do you want to take this one? It needs pinging KDE people (look at previous KDE tickets) a bringing them here to figure out the details.

@jgroman Do you want to take this one? It needs pinging KDE people (look at previous KDE tickets) a bringing them here to figure out the details.
jgroman self-assigned this 2026-07-27 07:51:55 +00:00
Owner

Pinging @ngompa, @tdawson, @sfaulken, @farchord

Hi guys,
we are planning to organize test week for KDE 6.7.x. Do you have any requests/suggestions regarding that, please?
Thanks!

Pinging @ngompa, @tdawson, @sfaulken, @farchord Hi guys, we are planning to organize test week for KDE 6.7.x. Do you have any requests/suggestions regarding that, please? Thanks!

Good question.... When are you planning on having said test days? Because we are getting close to a beta release of the new KDE Gear.

Good question.... When are you planning on having said test days? Because we are getting close to a beta release of the new KDE Gear.

Actually just noticed the beta is already out. We could do something based on that.

Actually just noticed the beta is already out. We could do something based on that.
kparal added this to the Fedora 45 milestone 2026-07-30 07:15:44 +00:00
Owner

@farchord wrote in #922 (comment):

Good question.... When are you planning on having said test days? Because we are getting close to a beta release of the new KDE Gear.

The date is not set, I was mostly checking if there would be some interest first.
New KDE Gear beta sounds good!

@farchord wrote in https://forge.fedoraproject.org/quality/tickets/issues/922#issuecomment-1072218: > Good question.... When are you planning on having said test days? Because we are getting close to a beta release of the new KDE Gear. The date is not set, I was mostly checking if there would be some interest first. New KDE Gear beta sounds good!

Yeah FYI the new Gear RC is pushed to rawhide. According to https://community.kde.org/Schedules/KDE_Gear_26.08_Schedule, August 14th is the date the final tarballs are made available to us.

Yeah FYI the new Gear RC is pushed to rawhide. According to https://community.kde.org/Schedules/KDE_Gear_26.08_Schedule, August 14th is the date the final tarballs are made available to us.
Owner

https://fedoramagazine.org/test-days-for-fedora-45-help-us-test-the-big-changes/
A reader pointed out that Plasma 6.8 will be released before F45 ships, so we should plan for 6.8 rather than 6.7.

https://fedoramagazine.org/test-days-for-fedora-45-help-us-test-the-big-changes/ A reader pointed out that Plasma 6.8 will be released before F45 ships, so we should plan for 6.8 rather than 6.7.

@psklenar wrote in #922 (comment):

https://fedoramagazine.org/test-days-for-fedora-45-help-us-test-the-big-changes/ A reader pointed out that Plasma 6.8 will be released before F45 ships, so we should plan for 6.8 rather than 6.7.

Plasma 6.8 is slated for release on October 14th: https://community.kde.org/Schedules/Plasma_6 wouldn't that be potentiallly too late (Or too short notice)?

@psklenar wrote in https://forge.fedoraproject.org/quality/tickets/issues/922#issuecomment-1340481: > https://fedoramagazine.org/test-days-for-fedora-45-help-us-test-the-big-changes/ A reader pointed out that Plasma 6.8 will be released before F45 ships, so we should plan for 6.8 rather than 6.7. Plasma 6.8 is slated for release on October 14th: https://community.kde.org/Schedules/Plasma_6 wouldn't that be potentiallly too late (Or too short notice)?
Owner

Yes, Final freeze is scheduled for 2026-10-06 . We can't be landing whole new releases of desktops a week after final freeze, really. For the test day, it's much better for it to happen at least a week before Final freeze so we can get fixes in without going through the FE/blocker process.

Yes, Final freeze is scheduled for 2026-10-06 . We can't be landing whole new releases of desktops a week after final freeze, really. For the test day, it's much better for it to happen at least a week before Final freeze so we can get fixes in without going through the FE/blocker process.

@adamwill wrote in #922 (comment):

Yes, Final freeze is scheduled for 2026-10-06 . We can't be landing whole new releases of desktops a week after final freeze, really. For the test day, it's much better for it to happen at least a week before Final freeze so we can get fixes in without going through the FE/blocker process.

Yeah submitting bugfix releases through freeze is fine, but full-on new major versions? Nah I'm not that crazy XD

@adamwill wrote in https://forge.fedoraproject.org/quality/tickets/issues/922#issuecomment-1340690: > Yes, Final freeze is scheduled for 2026-10-06 . We can't be landing whole new releases of desktops a week after final freeze, really. For the test day, it's much better for it to happen at least a week before Final freeze so we can get fixes in without going through the FE/blocker process. Yeah submitting bugfix releases through freeze is fine, but full-on new major versions? Nah I'm not that crazy XD

Well, the tarballs for Plasma 6.8 will be released on October 8. If we had the beta in now and iterated on betas during the development cycle, how does that change your thesis?

Well, the tarballs for Plasma 6.8 will be released on October 8. If we had the beta in now and iterated on betas during the development cycle, how does that change your thesis?

Nevermind, my question is dumb. The schedules are still too screwy for this. ☹️

Nevermind, my question is dumb. The schedules are still too screwy for this. ☹️
Owner

Let's just ship 6.7 and then do 6.8 as a post-release update, it'll be much less hairy.

Let's just ship 6.7 and then do 6.8 as a post-release update, it'll be much less hairy.

Yeah so I get that Fedora 45 final will be on 6.7. Is there a precedent though for building a new major version in copr and adding that to the test days, on top of the normal F45 tests? I'd like to contribute to upstream's efforts to make a stable final 6.8 release.

If not, that's fine too.

Yeah so I get that Fedora 45 final will be on 6.7. Is there a precedent though for building a new major version in copr and adding that to the test days, on top of the normal F45 tests? I'd like to contribute to upstream's efforts to make a stable final 6.8 release. If not, that's fine too.
Author
Owner

I see two options:

  1. Run 6.7 and 6.8 test days separately. We can run 6.7 some time in September (earlier is better), and 6.8 at any point that works best for you (it can be even after F45 release, if you wish) - we're no longer tied to any F45 schedule.
  2. Run 6.7 + 6.8 test days together. We would probably instruct people to first test 6.7, and then make a full system upgrade from copr to receive 6.8, and test 6.8. Or ask people to test 6.8 from a livecd instead. It depends if they can downgrade back to 6.7 afterwards, can they? (Having the 6.8 as a livecd is a good idea either way, though). In this case, the timing of the event would need to work both for F45 and for your 6.8 beta testing. Maybe the middle or the second half of September?
I see two options: 1. Run 6.7 and 6.8 test days separately. We can run 6.7 some time in September (earlier is better), and 6.8 at any point that works best for you (it can be even _after_ F45 release, if you wish) - we're no longer tied to any F45 schedule. 2. Run 6.7 + 6.8 test days together. We would probably instruct people to first test 6.7, and then make a full system upgrade from copr to receive 6.8, and test 6.8. Or ask people to test 6.8 from a livecd instead. It depends if they can downgrade back to 6.7 afterwards, can they? (Having the 6.8 as a livecd is a good idea either way, though). In this case, the timing of the event would need to work both for F45 and for your 6.8 beta testing. Maybe the middle or the second half of September?

Yeah so plan for the 6.7 test now. We're getting access to the tarballs in 8 days. My worry is that we might need to update a build requirement that we do not have direct access to or that we need help from another sig on (i.e. new rust requirements for example) and that holds us back. Once I have the stack built in copr, I can let you know and we can get the 6.8 test ready as well.

Yeah so plan for the 6.7 test now. We're getting access to the tarballs in 8 days. My worry is that we might need to update a build requirement that we do not have direct access to or that we need help from another sig on (i.e. new rust requirements for example) and that holds us back. Once I have the stack built in copr, I can let you know and we can get the 6.8 test ready as well.

Oh and to answer your downgradability question, technically yes you should be able to. From a software standpoint, all you need to do is disable the copr and run a dnf distro-sync and it'll downgrade everything. The worry comes from the user settings.

They can either create a secondary user, logout, drop in tty, upgrade, reboot, login to second user and do testing. When done testing, logout, drop in tty, disable the copr repo, distro-sync, reboot, login to original main user and they should be fine.

Or, backup their home folder, logout, drop in tty, update, reboot, test, once done, do the same thing in reverse with distro-sync and if something is wrong, restore the home folder.

But I've done a downgrade in the past and it worked fine. But it may introduce corruption as you may imagine.

Oh and to answer your downgradability question, _technically_ yes you should be able to. From a software standpoint, all you need to do is disable the copr and run a `dnf distro-sync` and it'll downgrade everything. The worry comes from the user settings. They can either create a secondary user, logout, drop in tty, upgrade, reboot, login to second user and do testing. When done testing, logout, drop in tty, disable the copr repo, distro-sync, reboot, login to original main user and they should be fine. Or, backup their home folder, logout, drop in tty, update, reboot, test, once done, do the same thing in reverse with distro-sync and if something is wrong, restore the home folder. But I've done a downgrade in the past and it worked fine. But it may introduce corruption as you may imagine.
Author
Owner

Ok, let's keep this ticket for 6.7 planning, and plan 6.8 in #935.

So, so do you have any preferred date for 6.7? It seems we can start preparing it immediately?

This is F44 test day for reference. I would say it would be good to extend the number of test cases. Thoughts?

Ok, let's keep this ticket for 6.7 planning, and plan 6.8 in #935. So, so do you have any preferred date for 6.7? It seems we can start preparing it immediately? This is [F44 test day](https://fedoraproject.org/wiki/Test_Day:2026-02-02_KDE_Plasma_6.6) for reference. I would say it would be good to extend the number of test cases. Thoughts?
kparal changed title from [F45 test days] KDE to [F45 test days] KDE 6.7 2026-08-19 11:27:58 +00:00

For 6.7, you can do so anytime it's fine. As far as the test cases, not sure maybe @ngompa can chime in

For 6.7, you can do so anytime it's fine. As far as the test cases, not sure maybe @ngompa can chime in
Owner

@farchord So I'd propose to do KDE Plasma 6.7 testdays 09/14 - 09/20 or the week after.

@farchord So I'd propose to do KDE Plasma 6.7 testdays 09/14 - 09/20 or the week after.

Fine with me.

Fine with me.
kparal added the due date 2026-09-10 2026-09-01 15:32:02 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

2026-09-10

Reference
quality/tickets#922
No description provided.