FinalBlocker +1

FinalBlocker +1

FinalBlocker +1

Local tracing works, but remote tracing seems to not work at all, again. And that could I guess be considered a basic functionality of abrt.

FinalBlocker +1

FinalBlocker +1

So, for F33, we rejected a more or less identical bug:

• https://bugzilla.redhat.com/show_bug.cgi?id=1885154 (bug)
• https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2020-10-05/f33-blocker-review.2020-10-05-16.00.log.txt (meeting log)

We generally aim for consistent decisions across releases, it's a key part of why the criteria exist. We have not changed any criteria here. So I would vote -1 again for consistency. We also got -6 at the meeting today, including sumantro changing vote from +1 here, so the vote stands at -6/+4. Does anyone want to reconsider their vote, or suggest another way to come to a clear consensus here?

Discussed during the 2021-09-27 blocker review meeting: [0]

The decision to delay the classification of this as a blocker bug was made as the current vote is not clear on this one; we will note the F33 decision in the ticket and see if anyone who voted +1 wishes to reconsider, or if any other way to resolve this appears.

[0] https://meetbot.fedoraproject.org/fedora-blocker-review/2021-09-27/f35-blocker-review.2021-09-27-16.00.txt

Changing my vote to be in line with F33 decision:

FinalBlocker -1

So, let me re-count the votes combining votes here and meeting votes:

• sumantrom -1 (changed in meeting)
• imsedgar +1
• lruzicka +1
• kparal -1
• frantisekz +1
• adamwill -1
• bcotton -1
• pwhalen -1
• southern_gentlem -1
• geraldosimiao -1

That gives us a total of +3/-7 , which is -4, so let's call it:

AGREED RejectedFinalBlocker

The following votes have been closed:

• Rejected FinalBlocker (+4, 0, -1)
  • +1 by sumantrom, imsedgar, lruzicka, frantisekz
  • -1 by kparal

Ack :)

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