> Currently, Nevada development has surpassed build 75 than Indiana is based > upon. This means that either Nevada development must stop and wait for > Indiana to catch up, and then push the Indiana framework into the head of the > Nevada tree, or throw away the current tree and reimplement in the Indiana > branch.
No, the Nevada branch will continue as it's always been. The prototype ISO was based on build 75a since we need to have a base to stablize the ISO around. Our expectations is that we will be working on pushing out revised bits via the package repository, perhaps as often as every two weeks following the release of SXCE. > It also means that, since the expected release cycle of Indiana is much > longer than the release cycle currently employed in SXCE/SXDE, some features > that are being worked on may not be tested in a timely manner (before > distribution). I assume there will be interim development releases between > official Indiana releases, like SXCE is to SXDE? For example, Indiana > doesn't have the Xen dom0 bits, so how would that be deployed properly? Again, we expect to have revised bits in the package repository on a regular basis. From those bits, creating a revised ISO should be a fairly straighforward process. By the way, although the ISO did not have the xVM dom0 bits, our package repository will have them so stay tuned - we hope to provide them shortly. dsc _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
