[arc-discuss] Defining OpenSolaris Consolidations

[John Plocher]

Alan Coopersmith wrote:
> [For the definition of Consolidation see:
>        http://www.opensolaris.org/os/community/on/os_dev_process/ ]

A Consolidation has both a specific meaning and a general one.  The
definition referenced above only touches on the general meaning - that
is, a named collection of source code releases that are managed as a
unit.  (This management usually consists simply of chartering new
instances of the consolidation under the Release Taxonomy).
Example:  ON

The specific meaning is that of a versioned instance of a general
consolidation - sometimes called a "gate", which is many times
managed by C-Teams.
Examples: ON-28, ON-8.1, ON-10, ON-NV, ON-10u4-patch. etc.

A proposal that deals with Consolidations needs to address the
need for a Consolidation to create and manage versioned instances
of its stuff.

------

Since you talk about Consolidations, C-Teams and W-Teams, here are the
definitions from Sun's Software Development Framework (SDF).
(FCS = First Customer Shipment = Revenue Release = General Availability)

> Introduction to the W-Team
> W-Team Purpose
> 
>     The W-Team's function is to take consolidations produced by
>     C-Teams and combine them to create a Product, which consists
>     of several compatible Consolidations that are shipped as a unit
>     to Sun customers. It also has an ongoing responsibility to
>     certify Products released later that claim compatibility.
> 
>     The W-Team is responsible for the DEV, Alpha, Beta, and FCS
>     cycles of selecting/building/validating its Consolidations. In
>     addition, the W-Team is responsible for internal and external
>     customer testing, the product announcement, and pre-FCS material
>     production. The W-Team members perform all activities required
>     before production and distribution, including: writing the
>     Marketing Plan and Service Plan; creating Material Forecasts,
>     Bills of Materials, and Engineering Change Order; creating
>     master documents and media; and procuring material.
> 
> W-Team Character
> 
>     The W-Team work is usually clearly defined because the W-Team
>     coordinates the activities of C-Teams and follows established
>     procedures for external testing, release engineering, and
>     production. Because the W-Team activities are done by several
>     functional groups working together, formal meetings are
>     particularly important.
> 
>     The W-Team is always a group of people (as opposed to an I-Team
>     which may be just one person). The Steering Committee must have
>     authorized the Project Plan for each Consolidation required by
>     name in the W-Consolidation Orders that charter the W-Team.
> 
>     W-Team members work to release the efforts of many C-Teams. The
>     value of each C-Team project is usually considered as it relates
>     to other projects making up their W-Consolidation at hand.
>     W-Team members are responsible for time schedule, quality, and
>     content of the finished Product.
> 
> 

and


> C-Team Introduction 
> C-Team Purpose
> 
>     The purpose of the C-Team is to take the components from several
>     I-Teams, integrate them into a build, test the build, and deliver
>     it to the W-Team as a consolidation from one major area (such
>     as OS/Net).
> 
> C-Team Life Cycle
> 
>     A C-Team's life begins when the Steering Committee (SC) issues
>     C-Consolidation Orders, which authorize the C-Team. C-Teams
>     remain in existence at least until the product's FCS version
>     is built by the W-Team.
> 
>     The C-Team develops the proposed C-Consolidation Plan, which
>     specifies the build process, schedule, and resources, as well
>     as the plan for testing the consolidation builds. The Plan also
>     includes the completion criteria, which are used to determine
>     if the deliverables (software and documents for each build,
>     including the final build) are finished and meet the agreed-upon
>     quality.
> 
>     The C-Team works closely with the W-Team, which manages and
>     integrates the various C-Team deliverables (documents and
>     software builds) for each of the product build/validation cycles.
>     C-Team test engineers file bug reports for bugs they find, which
>     are fixed by an I-Team created for that purpose.
> 
>  C-Team Membership
> 
>     C-Teams are typically made up of representatives from the
>     following areas: Build Engineering (to perform builds and
>     packaging), Test Engineering (to validate the integrated builds),
>     and Technical Publications (to prepare the documentation
>     consolidation). For products comprising only one consolidation,
>     the C-Team may be simply an individual known as the buildmaster.
>