Appreciate having some lead-time (~2 weeks) before beta freeze to adapt this time. Even better would be to do something like this idea expressed in chat today: "one possible idea: after fX is branched, you add to rawhide the "artwork" for fX+1... which is nothing else than a copy of the fX artwork" Then the new artwork could land any time (early the better of course), while packaging and DEs could have even longer to adapt.

Appears the SSH plugin is a new feature and not enabled by default, but we can look into it.

tarball sources are made available to distribution packagers for a brief period before formal upstream release and announcements.

For example, see release schedule: https://community.kde.org/Schedules/KDE_Gear_21.08_Schedule

Interesting, I cannot reproduce that, but will continue to watch the referenced upstream bug (thanks).

double click behavior is intentional, I believe, https://pagure.io/fedora-kde/SIG/issue/17

sorry for any fallout.

I expired the override causing broken deps, https://bodhi.fedoraproject.org/overrides/aom-3.1.1-1.fc33

Can you either add those dependant pkgs to f33-override too, or remove the aom override? Otherwise, some koji has a broken dependency currently building f33 targets: gstreamer: DEBUG util.py:444: - nothing provides libaom.so.2()(64bit) needed by gstreamer1-plugins-bad-free-1.18.2-1.fc33.x86_64

Sorry wasn't aware of that (f34 autoqa), I think upstream identified the commit that introduced the regression, I'll test reverting that asap.

Probably going to go stable with this despite there being a minor regression in konsole... initial size being bad (easy workaround, resize to something good once)

Situation improved (though still not perfect) in my testing so far, I'll report details in the bug once I verify/reproduce a couple more times.

Fixes bug #1925346 for me, yay

We really need more than 2 days of testing between submission and when big updates like this go stable (may need to disable autokarma for plasma updates for posterity).