On Tue, 17 Jul 2007, [EMAIL PROTECTED] wrote: >> Do I understand correctly that it won't/can't include anything that >> isn't ARC-reviewed or ARC-review-bound? > > Certainly before any changes are committed to the current > consolidations, they will need to be ARC reviewed. However, I envision > the initial previews being created out of "project" gates - perhaps the > existing consolidation packages are used from a content perspective but > the new installer or new packaging system or even a refactoring of the > existing package boundaries may take place in a project gate which > might not have been ARC reviewed. > > When the project gates integrates into their respective consolidations, > all the corresponding changes will have needed to be ARC reviewed.
And Dave Miner wrote: = ... Delivering a preview release in the short timeframe that's been = targeted here requires a relentless focus on specific tasks that are = primary to that deliverable, and deferring the things that aren't... [light bulb goes on] Thanks, this is very helpful and now I get it. (I'm still in the camp that wants a core thing for the 1st release, but because it's a minority camp, plus with the above explanation in mind, FWIW, I'm now happy to, as they say, disagree and commit.) Anyway, here's my way of grokking what you guys are saying (of course let me know if I don't have it right): The October preview release can include stuff (indeed *lots* of stuff) that hasn't been ARC-reviewed yet, which means the project can be unusually aggresive (new feature-wise) with the October preview release. And therefore, an all-out focused effort (per Dave M's reply) is called for -- leaving insufficient time to deliver an incremental core distro release between now and October. Eric _______________________________________________ indiana-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
