> Hi, > > I'd like add https://bugzilla.redhat.com/show_bug.cgi?id=1088619 > as blocker to release 21 . Please read last comments #95 still #101 Hello, you can always do that using https://qa.fedoraproject.org/blockerbugs/propose_bug However, that bug is quite a mess. When proposing as a blocker, it would be a good idea to create a new, concise one dealing with exactly one problem, instead of several problems merged in a single report. Or, at least, the explanation provided when proposing that blocker should be really descriptive, summarizing what the problem is, what the impact is and what needs to be done to resolve it. If I have understood the remaining problem well when skimming that bug, there is a delay before rebooting/shutting down. I agree that's inconvenient, but it doesn't seem to violate any of our criteria. Usually blockers are bugs which are very severe or can't be fixed post-release in a reasonable way. This can be fixed post-release. Because this bug is present for a very long time (I've seen it numerous times myself), it's questionable whether we should hold Fedora 21 release because of it. Either it's not easy to fix, or nobody cares too much about it. Probably the former in this case. And, the blocker process should not serve as a whip for developers "do finally something about this!". So, there's a high chance this would get rejected. But, if you feel this really is a release blocker material, feel free to propose it. Just please provide a reasonable summary, as described. Thanks for helping out with Fedora QA! -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
