> 1) How certain does it look right now that the UI rewrite will go into > F17? I plan on having at least a simple but usable new UI in F17. It may lack some of the bells and whistles in the mockups, and as previously mentioned it may lack a text mode interface. I would think that by F18, that kind of stuff would be present. > 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? No, I have no schedule. As of last night, there is code in rawhide. However it's all on a separate branch. On that branch, all the old UI code is still there but just disabled so we boot into the new UI by default. My plan is to continue working on the new UI on that branch, periodically rebasing to pull in non-UI commits. When it's looking solid (that is, when it actually does installs) I'll merge the branches. I'd like to not plan for failure to deliver, but if that happens, we can just not merge the branch. The existing UI will likely stagnate as a result, but whatever. Testing - no code yet, but I have ideas. See http://clumens.fedorapeople.org/UI/ui-tech-notes. Because this is just an anaconda branch, we can do periodic scratch builds and composes from it for others to look at. I think it'll be a while before there's much point in giving it any broad distribution though. This may be a good use of our computing power and disk space on the new cutlet. > 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? We've done extensive talking about use cases, but have not referred to the release criteria and test matrix. I suppose we should give it a look. I'm sure there will be some things that need to change on either side. > 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. Since I'm taking the lead on this project, I have a vested interest in making sure it's not a total disaster. So yeah, let's get talking about how to test this now. I'll start with looking at cutlet and doing automatic composes for internal testing. I wouldn't mind them getting distributed but right now, there's really no point. The new UI doesn't let you do anything. - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
