> And maybe even eat some hot dogs while we do! I'll have to check the google maps around the venue again. I'd done that earlier and discovered there's at least a Five Guys within walking distance, so we can make the mountain of uneaten fries once again. > So plan's to figure out how we can coordinate QA work for Anaconda > better in the (near) future, how and what parts we can test early (the > rewrite will likely make us want more QA/bugfixing time, and so do > other F17 features), what we should pay special attention to, and much > more! If time and progress allows we could also already get started > with testing and if QA folks' talk starts to bore you, you can always > ignore us and hack on Anaconda... The main goals for F17 are the UI rewrite (probably not the full design implemented, but everything required to get an install done) and the livecd creation tools rework. By FUDCon, I hope to have a large amount of the UI code done. I think it will then be too late to talk about what we should do for making sure the UI is testable. We'll have a lot of code that might need to be redone. So if we can start talking about what we can do now, I can build in whatever's needed. Then at FUDCon we can talk about how useful it is and what improvements we could make. Of course, we can also talk about non-UI testing stuff. > So, what do you guys think? Good idea? Bad idea? How much time should > we plan? Right now we figured half a day (~4h) would be nice. What > works best for you folks, Fri/Sat/Sun Morning/Afternoon? What other > important things should get done? Any time works fine for me. My FUDCon schedule is pretty flexible, given that I'm driving down there and don't have any plans for giving talks. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
