Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2131796 ** Information from BlockerBugs App:
The votes have been last counted at 2022-10-06 08:52 UTC and the last processed comment was #comment-820221
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
FinalBlocker -1 FinalFE +1
Since this isn't a default package, it's not a blocker. Unless it turns out that the fault is in Nautilus and is more easily triggered than this report suggests.
"If nextcloud-client-nautilus is installed..." Not part of the default install... so it could be a 0day?
0day means "it's a blocker but it doesn't have to be fixed in the base repo", meaning it's enough to have it in updates, or it's some other (non-development) task that needs to be done before the Final release is announced. So the same criteria apply, but it can be fixed a little later than usual.
0day
In this case, it doesn't make sense, because nextcloud-client isn't relevant to any our release criteria.
ok, thanks Kamil. so: FinalBlocker -1 FinalFE +1
AGREED RejectedFinalBlocker AGREED AcceptedFinalFreezeException
The following votes have been closed:
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F37 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.