How to deliver from one stream to another stream

If you are using 3.0.1, you can deliver directly from one stream to
another from the Pending Changes view (as long as there are no
conflicts). If there are conflicts (or if you are using a release that
doesn't support inter-stream delivery), you would use a workspace (i.e.,
accept all changes from both streams into the workspace, and then
deliver the result to the x_main stream).

Cheers,
Geoff

On 7/8/2011 11:38 AM, mehulnp wrote:

I have 2 stream release

x_main and x_rel_1.0.2

How can i deliver the source from x_1.0.2 to x_main release

Thanks

Hi Geoff,

we are using 2.0 and not 3.0.1

so for 2.0 the workspace has to be created of source stream or target stream. ?

i.e do we need to create the workspace off the source stream and accept all the changes from source stream and target stream ? and deliver the code to target stream ?

If you are using 3.0.1, you can deliver directly from one stream to
another from the Pending Changes view (as long as there are no
conflicts). If there are conflicts (or if you are using a release that
doesn't support inter-stream delivery), you would use a workspace (i.e.,
accept all changes from both streams into the workspace, and then
deliver the result to the x_main stream).

Cheers,
Geoff

On 7/8/2011 11:38 AM, mehulnp wrote:

I have 2 stream release

x_main and x_rel_1.0.2

How can i deliver the source from x_1.0.2 to x_main release

Thanks

Yes, in 2.0, you must use a repository workspace to move between streams.

Here's the easy way, for a simple case.

1. Create a workspace. Associate it with the source stream and load it.
2. Associate the workspace with the target stream.
3. Go to the pending changes view
4. Deliver change sets.

It doesn't really matter whether the workspace is first associated with
the source stream or the target stream. The only thing that matters is
that you accept the changes from the source stream into your workspace,
and then deliver those changes to the target workspace.

But since you first need to accept the changes from the source stream,
you would minimize the number of gestures needed if you create the
workspace on the source stream.

If the deliver operation fails saying you cannot deliver to the target
stream because there are conflicts, then you'd have to accept changes
from both the source and target stream, before delivering to the target
stream, because that is what allows you to resolve the conflicts by
merging in the workspace before delivering.

Even if there is not a conflict, in most cases I would recommend
accepting all changes from both streams into your workspace before
delivering, so you can at least do some kind of smoke test on the
combination, before delivering.

Cheers,
Geoff

On 7/8/2011 1:23 PM, mehulnp wrote:

Hi Geoff,

we are using 2.0 and not 3.0.1

so for 2.0 the workspace has to be created of source stream or target
stream. ?

i.e do we need to create the workspace off the source stream and
accept all the changes from source stream and target stream ? and
deliver the code to target stream ?

gmclemmwrote:
If you are using 3.0.1, you can deliver directly from one stream to
another from the Pending Changes view (as long as there are no
conflicts). If there are conflicts (or if you are using a release
that
doesn't support inter-stream delivery), you would use a workspace
(i.e.,
accept all changes from both streams into the workspace, and then
deliver the result to the x_main stream).

Cheers,
Geoff

On 7/8/2011 11:38 AM, mehulnp wrote:
I have 2 stream release

x_main and x_rel_1.0.2

How can i deliver the source from x_1.0.2 to x_main release

Thanks