James Carlson wrote:
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.
*Exactly* what I was referring to with the "source base, not a binary
deliverable is a quagmire" comment I made earlier in this thread.
-- Rich
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
