* John Plocher <[EMAIL PROTECTED]> [2007-01-09 10:11]: > James Carlson wrote: > >Cyril Plisko writes: > >>On 1/9/07, Darren J Moffat <[EMAIL PROTECTED]> wrote: > > > ... lots of thoughtful stuff ... > > I don't understand where this view that OpenSolaris > Communities don't have releases came from. > > Using old Sun terms, while the OpenSolaris effort isn't > interested in taking all the code it hosts and making it > into a product, those various Consolidations certainly will > want to manage their code bases and schedule releases of > their components. > > The "process change" that needs to happen is that the chartering > of releases (the Major, Minor, Micro stuff) that *was* done > by Sun Product Approval Committees (PACs) now needs to be > managed by the communities themselves. And by community, I > mean the ON Community Core for the ON releases, the Desktop > Community Core for the Desktop releases, etc, not the OGB.
+1. 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. - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems [EMAIL PROTECTED] http://blogs.sun.com/sch/ _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
