Richard Lowe writes: > > What exactly are you looking for here? The project name (it's "Zulu," > > if that helps)? > > > > Yes, that does help, but only because it's then possible to infer > exactly what is being talked about. > > Just a black box 'something went wrong, somewhere' really tells people > nothing...
Solaris is made up of a large number of consolidations. In order to produce the bits that show up in a build (such as SX:CR), these consolidations deliver packages to something called the "integration dock." The WOS people then turn the crank and produce the DVD and CD images out of those packages. The consolidations are all different and each operates by a different set of rules. Not all of them build or deliver packages every two weeks. Some of them are highly automated, others are not. Some consist of thousands of people (ON), others are just a handful. In this case, one of the gatekeepers for one of the consolidations accidentally invoked the deliver-these-bits-to-the-WOS script when he meant to invoke a script that would build a DVD for an undelivered project. I don't agree that the original response was quite that vague, but in fact the answer itself is awfully short: someone just made a simple mistake. It wasn't a complicated problem, so there really aren't any details to hold back, or to explain. Just "oops." It shouldn't have happened, but it did. It's over now, except for the flame war. :-/ -- James Carlson, KISS Network <[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-discuss mailing list opensolaris-discuss@opensolaris.org
