On Mon, Jan 25, 2016 at 9:59 AM, Paul W. Frields <stickster@xxxxxxxxx> wrote: > IIRC we aren't blocking on LUC currently -- so whether this means > reviving old criteria or creating new ones, that needs to be clear. > OTOH, the functions of LUC are pretty well constrained. So maybe this > isn't too large a change. Well if LUC is blocking on Linux, Windows, and OS X, that's three rows added to a matrix that has the same number of column as the total number of release blocking media per arch. So that's possibly a lot more testing, even if the only thing used by LUC on the backend is wipefs and dd. If it's different from dd in any way, then LUC tests can't be used as a substitute for testing with dd alone, because it couldn't be dropped as a release blocking method for media creation. The media erase/restore option should probably be a non-blocking testcase. If there's going to be a persistent overlay optional, it should also be non-blocking. -- desktop mailing list desktop@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/desktop@xxxxxxxxxxxxxxxxxxxxxxx
