release criteria, data corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://fedoraproject.org/wiki/Fedora_21_Final_Release_Criteria#Data_corruption

I suggest moving this criterion from final to beta due to bugs like this one:
https://bugzilla.redhat.com/show_bug.cgi?id=1120964

Beta is rather publicly marketed, and people are actively encouraged to participate. Many will do this with as dual-boot. I don't think it's OK for known corruption of existing user data (the entire prior OS) to progress to beta release; but aside from that, and the ensuing negative experience it'd cause, it also significantly reduces the test coverage because we'd have to say "Hi, we want you to test beta but not in a dual boot scenario with Windows."

Alternatively make a new beta criterion that explicitly blocks on corruption of existing user data, rather than corrupting newly generated data.


Chris Murphy
-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux