Darren.Reed at Sun.COM wrote:
> Gary Winiger wrote:
>>
>> Please follow the template. ON is not a release vehicle:
>>
But it is, and the template is correct. The coincidence that ON is
usually co-released with other consolidations as part of a product is
just that - a coincidence.
Gates, C-Teams and integrations don't apply to products like Solaris
or Belenix or Nextenta - instead they are associated with
consolidations; when we approve an ARC case, we are approving a change
to a specific consolidation instrance.
Note that there many ON consolidations in play at any given time:
The next Minor release:
ONnv
The Patch trains for the current Minor release:
ON-S10u1, ON-S10u2, ON-S10u3, ON-S10u4, ON-S10u5...
The Patch trains for earlier Minor releases:
ON-S9xxx, ON-S8xxx, ...
In an opinion, when we say...
> The project may be delivered in a minor release of the ON consolidation
... we are explicitly identifying which specific ON consolidations in
the set of all active ON consolidations are acceptable for the project
to integrate into. Not unintentionally, it also serves as the context
for all those project interfaces marked as Consolidation*Private.
Solaris (as in the DVD or vinyl binder of disks or SDLC download
images...) has been effectively staging Major releases for the
last decade or so - ever since things like try-n-buy, extra-value,
SFW, JES/iPlanet/Orion, Oracle and the like have been included
in the definition of the product.
Don't confuse Solaris (the umbrella product family) with either
the ON Consolidation or the core set of pseudo-stable consolidations
that have historically been known as the WOS - neither of these
collections are really relevant to the ARC's scope.
-John
