release criteria, data corruption

[Adam Williamson]

On Thu, 2014-07-24 at 16:14 -0600, Mike Ruckman wrote:
> On Thu, Jul 24, 2014 at 02:09:33PM -0600, Chris Murphy wrote:
> > 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
> 
> I'm +1 for at blocking at beta for *at least* the corruption of existing user
> data. 

I'm at least +/-0, probably a weak +1. Be nice to hear some comments
from dev side (e.g. anaconda devs) on this, though. Partition resizing
in particular is known and explicitly warned to be a dangerous operation
in the installer, I believe.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net