On Thu, 13 Oct 2011 12:03:02 -0700 Adam Williamson <awilliam@xxxxxxxxxx> wrote: > > - The release must boot successfully as Xen DomU with releases > > supporting Xen Dom0 and cloud providers utilizing Xen. > > 'With releases supporting Xen Dom0' is slightly vague but probably > good enough for now. I wanted to make sure that we weren't including F9 - F15 since they didn't officially support Xen. Eventually, we could change it to say current and previous releases. > I'm not exactly sure what we want to say about > the Dom0; I think the concept is that DomU functionality shouldn't be > broken, anything that's a bug on the Dom0 level isn't a blocker > issue, right? Yeah, I don't think that Dom0 issues should be included in the criteria. I'm not sure how to phrase DomU issues without bringing in some concept of Dom0, though since I don't think that you can have a DomU without Dom0 of some incarnation. My intention was to include issues with DomU running locally (with an already functional Fedora Dom0) or on a Xen based cloud provider. My implicit assumption was that Dom0 would already be working but since F16 is the first supported Dom0 since F8, that could be problematic. For F17 and later, I imagine that we could just say that it needs to run with a previous release as Dom0. Tim
Attachment:
signature.asc
Description: PGP signature
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
