#1284 [gnome-shell-extension-dash-to-dock] Pull in Dash to Dock with GNOME 45 Support | rhbz#2237658
Closed by blockerbot. Opened by blockerbot.

Bug details: ** https://bugzilla.redhat.com/show_bug.cgi?id=2237658 **
Information from BlockerBugs App:
2237658

Current vote summary

The votes have been last counted at 2023-09-11 17:08 UTC and the last processed comment was #comment-873593

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)


So how is this different to NeoChat in #1254? Dash to Dock is also not installed by default.
At the moment:
BetaFE -1

It addresses the case when users upgrade to the Beta release without updates-testing enabled. Also, we accepted these as FE in the past [0], so...

[0] https://pagure.io/fedora-qa/blocker-review/issue/1059

BetaFE +1

That's a good link. It seems we need some better defined guidelines, because I don't see why a dock should work after system-upgrade but a chat client shouldn't. I'd like to be consistent.

From #1059:

Folks might want to use it on the lives

I don't understand this, installing it from the network will pull it the working version (because updates-testing is enabled on Lives - even though currently it isn't, which is a bug to be fixed).

Consistency is overrated!

Fine, we should probably be stricter...this can just be an update.
BetaFE -1

The good thing about being stricter is that eventually proposers will give up and we'll have less work 😆

That's an exaggeration, of course. The basic guidelines for FEs are in Freeze_exception_bug_principles. If anyone thinks we should adjust it, please propose a change on the test list. Note, those are just guidelines, the process is flexible, but if something is e.g. easily fixed by an update, we should at least hear a good reason to deviate from the guidelines, I believe. As for "people might update without updates-testing", I think we'll need to start assuming our pre-Beta testers are capable enough to either enable it during system-upgrade, or be able to cope with the issues until they run dnf update after the system-upgrade. Otherwise a large portion of existing frozen updates would be eligible for an FE, and I don't think we want or have the capacity to go this route.

The following votes have been closed:

Metadata Update from @blockerbot:
- Issue status updated to: Closed (was: Open)

Release F39 is no longer tracked by BlockerBugs, closing this ticket.

Log in to comment on this ticket.

Metadata