Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2139092 Information from BlockerBugs App: <img alt="2139092" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2139092" />
The votes have been last counted at 2022-11-04 19:45 UTC and the last processed comment was #comment-824711
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
This is issue #1000 ! 🥳 🎉 😉
That surely deserves a recursive reference... :wink: :100: :x: :keycap_ten:
FinalBlocker +1
This is clearly not quite the behavior upstream intended.
based on my investigation and understanding, I'm pretty sure the notification would just never show, and that's not what upstream or our KDE team intended.
Note, though, that this is a sort of odd state: Plasma 5.26 itself is only an FE, not a blocker. So the state of this would be sort of "it's a blocker if we're pulling in 5.26, it isn't if we're not".
now there's an MR upstream: https://invent.kde.org/plasma/discover/-/merge_requests/404
That should translate into "404: Notifications not found" :smirk:
Also, with Adam's remarks.
Oh... It's fixed now. Great.
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Login to comment on this ticket.