#973 [mesa] Consider mesa-22.2.2-1 pull into F37 | rhbz#2134742
Closed by blockerbot. Opened by blockerbot.

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

Current vote summary

Commented but haven't voted yet: adamwill, nielsenb, coremodule, kparal

The votes have been last counted at 2022-11-01 09:23 UTC and the last processed comment was #comment-823728

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)


This seems like a tricky call for non-specialists - you can look at the changelog but unless you know what a turnip is (probably not the tuber, but I wouldn't swear to it) and what "buffer sharedness tracking" and "rayquery lowering" are, it may not help much. So I've asked @airlied and @ajax to chip in with expert opinions if they can.

My inclination is to be -1 to prevent the risk of a last-minute disruption, but I'll hold my vote until Monday so that the experts have a chance to weigh in.

Well I'll wait for it too.
Is the actual mesa at stable repo broken, with security issues or with patented drivers?

Needs more info indeed. Will vote in meeting.

I can't make the meeting, so I'm going to pretend to be a domain expert now! :laughing:

Bugzilla isn't lighting up with "my graphics drivers are broken", and a quick skim of the changelog doesn't show anything that can't wait a day or two for an update. Given that Mesa is pretty core this feels high risk.

FinalFE -1

AGREED RejectedFinalFE

Discussed during the 2022-10-17 blocker review meeting: [0]

The decision to classify this bug as a "RejectedFreezeException (Final)" was made as nobody has provided a strong reason to pull this in and we have no evaluation from a domain expert, so it doesn't seem prudent to just pull this in and hope it makes things better.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-17/f37-blocker-review.2022-10-17-16.01.txt

The following votes have been closed:

  • Rejected FinalFreezeException (+0, 0, -1)

REVOTE FinalFE

This has been re-proposed due to the delay to Final. @ajax , @airlied , we could still really use your input here.

Sorry, @gui1ty , you'll need to vote again now.

Sorry, @gui1ty , you'll need to vote again now.

Third time lucky

FinalFE +1

Based on the input of maintainers

To which I replied:

How does this fare with

"This is pretty much what should have been in 22.2".

Repeating this here for people that may have missed the latest comments in the bug. I may re-consider my vote (unlucky me).

The intent of the proposal was in line with "let's get this in as users would get is as 0day anyway and we have bunch of time for testing now - similarly as why we're pulling new gnome/kde/kernel stacks in", not that there was anything critical fixed.

I am obviously:

FinalFE +1

Accepted as a freeze exception during a blocker review meeting:
https://meetbot.fedoraproject.org/fedora-blocker-review/2022-10-31/f37-blocker-review.2022-10-31-16.00.log.html

AGREED AcceptedFinalFreezeException

The following votes have been closed:

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

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

Log in to comment on this ticket.

Metadata