I don't have a strong opinion here. In any other app I'd just waive my hand, no harm done, but I feel we should have high standards when it comes to the package manager.

FinalBlocker +1

My $0.02: this one is iffy, but it's really weird and seems reasonable to classify it as a basic functionality failure.

FinalBlocker +1

I feel like this would probably fail the last blocker test if we hit it on Go/No-Go morning, so I'm:

-1 FinalBlocker
+1 FinalFE

FinalBlocker 0

But if I had to lean on one side, I'd probably chose -1 because the issue seems to be harmless, only confusing.

FinalFE +1
of course

FinalBlocker -1
FinalFE +1

Agreed that it's "confusing but harmless."

FinalBlocker -1
FinalFE +1

Arguments against making it a blocker are compelling. It's cosmetic, functionality isn't inhibited.

FinalFE +1
FinalBlocker -1

Its a good fix to have and will clarify the confusion, but we can work around it.

FinalFE +1
FinalBlocker -1

FinalBlocker -1
FinalFE +1

AGREED RejectedFinalBlocker AcceptedFinalFE

The following votes have been closed:

• Rejected FinalBlocker (+1, 1, -5)
  • +1 by catanzaro
  • 0 by kparal
  • -1 by chrismurphy, adamwill, bcotton, mohanboddu, kevin
• Accepted FinalFreezeException (+6, 0, -0)
  • +1 by adamwill, kparal, bcotton, chrismurphy, mohanboddu, kevin

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