Policies for deliver operations to nondefault targets
Some policies apply only to deliver operations whose targets are not the
default target streams. You can set these policies to apply to all streams
within the project or you can set the policies on a per-stream basis. When
a developer starts a deliver operation, UCM checks the policy settings on
the target stream and the project. If the target stream’s policy setting is
different than its project’s policy setting, the project setting takes precedence.
In a project, you can create a hierarchy of development streams. Such a
hierarchy as shown in Default and nondefault deliver targets in a stream hierarchy allows
you to designate a development stream as a shared area for developers working
on a particular feature. Figure 1: Default and nondefault deliver targets in a stream hierarchy
Developers who work on that feature deliver work to the feature-specific
development stream Feature1. In Default and nondefault deliver targets in a stream hierarchy,
the integration stream and the Feature1 development stream are ancestors
of the Developer1 and Developer2 development streams. The streams Feature1, Developer1,
and Developer2 are descendants of the integration stream. The
default target for a deliver operation from a development stream is the parent
stream of that stream. Developers may also deliver to nondefault target streams.
The arrows in Default and nondefault deliver targets in a stream hierarchy illustrate
default and nondefault deliver targets. The following policies apply only
to such nondefault target streams:
Deliver changes from the foundation in addition to changes from the stream
Allow deliveries that contain changes to missing or non-modifiable components
Allow interproject deliver to project or stream
Require that all source components are visible in the target stream
