Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2057719 Information from BlockerBugs App: <img alt="2057719" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2057719" />
Commented but haven't voted yet: coremodule
The votes have been last counted at 2022-03-07 22:19 UTC and the last processed comment was #comment-784816
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
BetaBlocker 0 BetaFE +1 FinalBlocker +1
We don't have an explicit networking criterion that I can find (an oversight perhaps?), but this would fall squarely under the "basic functionality" Final criterion
AGREED AcceptedBetaFE
Discussed during the 2022-02-28 blocker review meeting: [0]
The decision to delay the classification of this as a blocker bug and to accept this as an "AcceptedFreezeException (Beta)" was made as we do not have specific criteria for VPN connections, and trying to stretch existing criteria to fix this is difficult. We do have proposed specific criteria from 2020, so we will resurrect the discussion on those criteria and decide on blocker status when that's done. This is definitely serious enough to grant an FE, though.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-02-28/f36-blocker-review.2022-02-28-17.00.txt
The following votes have been closed:
Same reason as for enterprise wifi – vpn is important e.g. it is the only way to access some university services from outside of the university network.
BetaBlocker 0
BetaBlocker -1 FinalBlocker +1
We should not actually delay release on this: if the VPN plugins are not ready, then gnome-control-center is not ready either, and we should hold it back to version 41 rather than delay F36 release.
If you do this, this sounds a reasonable solution.
Agree with the above.
BetaBlocker -1 BetaFE +1 FinalBlocker +1
AGREED RejectedBetaBlocker AGREED AcceptedBetaFE AGREED AcceptedFinalBlocker
Discussed during the 2022-03-07 blocker review meeting: [0]
The decision to classify this bug as a "RejectedBlocker (Beta)", "AcceptedBlocker (Final)", and an "AcceptedFreezeException (Beta)" was made as this does not violate the current Beta criteria, and there wasn't enough support for applying the proposed networking criteria that do cover it to F36 Beta, but it is bad enough to be an FE. For Final, it violates the default app functionality and panel criteria.
[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-03-07/f36-blocker-review.2022-03-07-17.01.txt
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.