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

Some questions about UI rewrite plans, timeframes and testing



Hey, anaconda team!

So now we got F16 out of the way, we (QA team) are starting to think
ahead to F17, and obviously, one of the big things currently slated to
land in F17 is the anaconda UI rewrite. We'd like to do all we can to
avoid the kind of last-minute rush and extreme pressure we all were
under for F16, so we're trying to think of ways we can ensure the UI
rewrite doesn't disrupt the F17 release process excessively.

So, with that background, a few questions:

1) How certain does it look right now that the UI rewrite will go into
F17?

2) Is there a precise schedule for the UI rewrite to land, or is it more
a case of 'we'll land it when it's done'? If the latter, do you have a
hard date beyond which you would not land the rewrite, considering it to
be too late?

3) Do you have any plans in place so far for testing the UI rewrite? Are
there plans to get something buildable available early? Do you have any
plans along the lines of making test images available, or do we have a
blank slate to work from there at the moment?

4) Have you taken into account all the use cases and required
functionality implied in the release criteria and installation
validation matrix in the re-design?

That's what I've got for now. Ultimately I'd like to work together to
come up with a process so we can start testing the UI rewrite early and
be able to test it continuously, with the hope that we can isolate
potential problems early in the cycle and get them sorted before we
start hitting the pre-release points.

Thanks!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net


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