BetaFE +1

BetaFE +1

BetaFE -1

This is a massive change (and commensurate risk) for a release-blocking desktop being requested one day before Go/No-Go. It's unfortunate and I recognize that there are significant Wayland fixes here, but during a Freeze we should really only accept targeted fixes, not massive rebases.

BetaFE -1

This is a massive change (and commensurate risk) for a release-blocking desktop being requested one day before Go/No-Go. It's unfortunate and I recognize that there are significant Wayland fixes here, but during a Freeze we should really only accept targeted fixes, not massive rebases.

This has been sitting in updates-testing for over a week now with no package changes and positive reports from users. The only reason it didn't have its FE filed for the desktop as a whole is because @rdieter, @jgrulich, and myself forgot until @adamwill reminded me on Monday.

Feedback in updates-testing is one thing, but this affects the compose, and that hasn't really been tested. It doesn't matter why the FE request was filed late, really, it's still a risk to pull it late.

I might be +1 to this if we slip a week. Maybe.

Feedback in updates-testing is one thing, but this affects the compose, and that hasn't really been tested. It doesn't matter why the FE request was filed late, really, it's still a risk to pull it late.

That makes very little sense, considering that we have no other options for getting things in the hands of users in a broad way. The argument for not doing so many composes is that they're not supposed to be considered fundamentally "special", but if we're saying that they are (and it sounds like you're arguing that), then we should be doing composes on updates-testing every night and testing that.

From my point of view, I have no other tools to make sure I don't get a ton of useless feedback if I don't get this into Fedora 34 Beta.

The point is, if it had been requested for an FE earlier, we could have pushed it stable and put it in a compose and if that had broken anything, we would have had time to figure it out.

It it goes into a compose for the first time at the last minute, there is no leeway to find and fix issues.

I'm marking this as accepted based on votes in discussion at the Go/No-Go meeting today (and shortly after the meeting ended). lruzicka, pwhalen, frantisekz, bcotton and copperi all voted +1. I'm also +1 since we have a slip. That's +6 and even if we still count sgallagh's -1, total is +5.

AGREED AcceptedBetaFE

The following votes have been closed:

• Accepted BetaFreezeException (+2, 0, -1)
  • +1 by bcotton, pwhalen
  • -1 by sgallagh

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