> Casper.Dik at Sun.COM writes: >> You can also ask why is the remark even there? It goes without saying >> that you are not allowed to break other projects when you integrate; >> unless the ARC explicitly approves such breakage. > > Certainly true. Project teams are responsible for making sure that > they don't break anything, and doing any required testing to prove > it. That's not an ARC issue -- it's a C-team review and development > process issue. > > In this case, though, Tim Marsland noted during the project review > that booting Xen instances is different, and the difference may have > escaped the attention of the project team. The project team members > agreed that they should talk with him, and make sure that Xen still > works. > > Our assumption at this point is that the project as specified is > complete and that no architectural changes will be required in order > to make Xen work. If that's not the case, then the project team will > need to file a new case in order to describe the required > architectural changes.
I talked to Lin immediately after the meeting; I also discovered (on IRC) that the relevant work (on libfsimage and pygrub) was already in progress -- and so I think the dots are nicely connected. Please, no more time or neuronal activity on this until (as Jim said) additional architectural review is needed. tim
