Stephen Hahn writes: > The authority to identify a release species and manage integrations > moves from internal Sun committees to the Community Group that is > publishing a Consolidation. (The role of the Governing Board in > coordinating among Community Groups is still to be determined.) > The engineering process wasn't discarded in this transition.
The odd thing about that is that the distributors are actually in control of when and how the releases themselves are generated -- they're the ones who type 'make' somewhere and ship the resulting bits. The Open Solaris community itself doesn't do that part. So, we have one central group defining the type of release that the source itself represents, but multiple groups independently attempting to schedule their own releases with their own content. Perhaps I'm just being dense about this, but something in there doesn't sound fully baked to me. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
