[F45 test days] KDE 6.7 #922
Labels
No labels
agile
anacondawebui
arm
blockerfe
Closed As
Duplicate
Closed As
Fixed
Closed As
Invalid
Closed As
Wontfix
Closed As
Worksforme
coreos
criteria
defect
easyfix
enhancement
iot
meeting
meta
onboarding call
proventesters
retrospective
silverblue
sponsor
test cases
test days
wiki
ai-review-please
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
pr2jira
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No project
No assignees
6 participants
Notifications
Due date
Blocks
#916 Plan F45 test days (Changes, usual events)
quality/tickets
Reference
quality/tickets#922
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
@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.
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.
Actually just noticed the beta is already out. We could do something based on that.
@farchord wrote in #922 (comment):
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.
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):
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)?
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):
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?
Nevermind, my question is dumb. The schedules are still too screwy for this. ☹️
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.
I see two options:
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-syncand 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.
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?
[F45 test days] KDEto [F45 test days] KDE 6.7For 6.7, you can do so anytime it's fine. As far as the test cases, not sure maybe @ngompa can chime in
@farchord So I'd propose to do KDE Plasma 6.7 testdays 09/14 - 09/20 or the week after.
Fine with me.