BetaFE +1

If this bug is not fixed by the update, it seems this could be a FinalBlocker as well. Broken tracker should render quite a few apps and their features broken.

BetaFE +1

BetaFE +1

The following votes have been closed:

• Accepted BetaFE (+3, 0, -0)
  • +1 by kparal, frantisekz, lbrabec

@frantisekz I know this is just an FE and not a blocker, but I feel that a ticket should be open at least for 1 day, ideally for 2, before we conclude the vote, so that everyone has at least a chance to react. (Unless we really want to include the update in the next push, in that case the fast track is of course fine). Wdyt?

@kparal The ticket is still open for discussion, however, we Accepted FEs after three +1 pretty much always... at least from what I remember.

And yes, I am including this in next stable push request [0]

[0] https://pagure.io/releng/issue/9725#comment-676218

@kparal The ticket is still open for discussion, however, we Accepted FEs after three +1 pretty much always... at least from what I remember.

Yes, but during a blocker review meeting, people don't risk not having their vote counted, because they're either present and can vote, or aren't present. I know we sometimes did "vote in bugzilla" and then "alright, we have 3x +1, accepted", but that was mostly for cases where we needed to votes really quick. So what I'm saying - unless we need the votes really quick, it would be good to give people from all timezones a chance to participate.

And yes, I am including this in next stable push request [0]

Alright.

I agree with @kparal. There is no need to resolve these tickets too fast. They will not run away. :D

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