* Richard Lowe <[EMAIL PROTECTED]> [2007-01-10 15:14]: > The more I think about it, the more messy having this kind of autonomy at > the consolidation level seems to become. > > Historically, as best as I know, it hasn't existed (though in the case of > JDS, it maybe somewhat present), I can't currently see any reason that it > must exist, or, frankly, any benefit (other than perhaps forcing cleaner > architecture) stemming from it. > > To take the hypothetical Major release further. JDS decides on a micro > release, SFW, X and Install decide on a minor release, on ON decides on a > major release. All niceties aside, what you're left with is unlikely to be > a product, but a mess. > > In theory, certainly, you could pick appropriate prior releases of > consolidations of a release of greater magnitude than your desires, > probably cherry picking changes from after that release to meet feature and > bug-count goals, but I doubt it would be pleasant, and of course, you'd > have to continue this until the planets aligned with your release goals. > > I guess I feel that the consolidated nature should remain, different > consolidations, all OpenSolaris, and that such things should be done as a > whole (perhaps by an appropriate group from each consolidation or whatever). > > Though little of this has any direct bearing on sch's initial request, but > I guess that's my fault. :-)
Well, before we get back to that (because you all agree with the proposal, and it is but for the assembly of a schedule that we aren't already doing things that way), I think it's important to recognize that the Governing Board could in fact reauthorize or amend the equivalent of the W-team orders so that aspects under which the consolidation-publishing communities run are being changed. I'm quite happy with the discussion, although my inclination is to get the immediate term issue resolved and then spend some time thinking about how the endgame of a specific release is handled. (I remember when Mike Shapiro was commenting on how it seemed everyone (who could have fixed an additional bug or two) suddenly departed from a release near closing and arrived at a shiny new gate--I think he called this the "ghost ship" phase, where the gatekeepers and a few others attempt to pilot the release for the last couple of builds. Of course, this is an ON story, and other consolidations may have better discipline.) One approach--of many possible--is for the OGB to convene a committee to examine, in some methodical way, the various possibilities and make a set of recommendations. I think this thread shows that there are a lot of factors to compare for each possible scenario. So... out of every 8 builds, the last two are restricted for stabilization? - 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
