BetaBlocker -1

The maintainer says it's working as expected and probably won't be changed.

BetaBlocker -1

The story seems more complicated than that to me; @lruzicka said he rebooted between attempts. It would be good if more people could test this and see how it goes for them.

The maintainer says it's working as expected and probably won't be changed.

Honestly, if the user presses the Refresh button and it fails to refresh available distro upgrades, that's just no good. Not a good expectation. Now, blocking release over this seems a bit harsh, but I see is a beta release criterion, and I'm satisfied that it is violated here. The user should not be expected to do anything more than Refresh to see the upgrade to Fedora 36.

BetaBlocker +1

Actually, this would need to be fixed in Fedora 34, not F36, so:

BetaBlocker 0
PreviousRelease +1

I tested this myself and didn't reproduce - I followed the steps in the test case, and Software showed the upgrade to F36 right away.

This specific case is really kind of wonky at Beta - we're really kind of forcing GNOME to do something different here. It's not exactly representative of how things will be at release time. So I don't think there's really a benefit in blocking the release on this. We don't really expect people to upgrade this way at Beta, in practice it's easier to just use dnf if you want to upgrade before the stable release. So I'm kinda not inclined to block unless it's utterly broken. I'm:

BetaBlocker -1

BetaBlocker -1

AGREED RejectedBetaBlocker

The following votes have been closed:

• Rejected BetaBlocker (+0, 1, -4)
  • 0 by catanzaro
  • -1 by bcotton, frantisekz, adamwill, ngompa

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