> From: bruno@xxxxxxxx > To: test@xxxxxxxxxxxxxxxxxxxxxxx > Subject: Should I make a tracking bug in fedora for problem reported upstream? > > I have reported https://bugzilla.kernel.org/show_bug.cgi?id=41862 for an > issue with 3.1 kernels crashing, typically on the order of hours after > booting. Based on some names in the traceback, I suspect this is MD raid > or luks related. > > I reported this upstream, since that seems to be a better place to get > attention for development kernel bugs, than Fedora's tracker. However, > if this should be considered a beta blocker, then I should probably also > make a Fedora bug entry so that it can be tracked as a blocker. > > However it doesn't seem to meet the explicit requirements for a beta blocker. > The only category it might fit in is a high severity bug. But if it really > limited to systems using MD raid or luks encryption, I am not sure if > it would meet that standard. > > If it isn't a blocker, I'd rather not enter a duplicate bug in Fedora since > that would just seem to be a waste of resources. (But maybe QA would rather > see the bug entry anyway.) I would stick in on b.rh.com and mark it as a blocker, since it does sort of block Beta criteria 5. John. -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
