Managing streams and changesets for different releases
This may be a beginner question; so please bear with us! We have been using RTC as source control for several months now and are generally happy with working in the client. Now we have reached the point where we want to create a new branch for starting work on the next version; while also making any important fixes to the older stream.
We can create a new stream easily enough (Create a snapshot of the current stream, create a new stream from that snapshot)
If we want to make a change to one of those streams and also apply the same change to the other stream; is there a better way than our usual old way of working (as with VSS) of making the changes twice (by merging over the changes and checking them into in both streams)?
We have spoken to another team who also moved to RTC from VSS and they have said that this is the only way they know how to work and it is what they are doing.
So; are we missing out on a better way of working? Can we flow changesets to multiple streams? Obviously some changes are going to be specific to individual streams, so we need to control what goes where; but if there's a better way of managing this we'd love to know.
Thanks.
We can create a new stream easily enough (Create a snapshot of the current stream, create a new stream from that snapshot)
If we want to make a change to one of those streams and also apply the same change to the other stream; is there a better way than our usual old way of working (as with VSS) of making the changes twice (by merging over the changes and checking them into in both streams)?
We have spoken to another team who also moved to RTC from VSS and they have said that this is the only way they know how to work and it is what they are doing.
So; are we missing out on a better way of working? Can we flow changesets to multiple streams? Obviously some changes are going to be specific to individual streams, so we need to control what goes where; but if there's a better way of managing this we'd love to know.
Thanks.
2 answers
You can change the flow target of a remote workspace and changes not in the target will become outgoing change sets. You can deliver those changes to the target (your new stream).
In Pending Changes view, right-click on your workspace and select 'Change Flow Target...' to flow your changes to the new stream.
In Pending Changes view, right-click on your workspace and select 'Change Flow Target...' to flow your changes to the new stream.
Also, note that an RTC repository workspace can have multiple streams as
its "flow targets", one of which is declared to be the "default" flow
target (the only semantics associated with the default flow target is
that you will be warned whenever you are delivering to a stream that is
not marked as the default flow target for that repository workspace).
Whenever you pick a new stream as a flow target, it gets added to this
list (open up the workspace in the workspace editor, and you can view
and manipulate all of the flow targets of the workspace).
Cheers,
Geoff
tmok wrote:
its "flow targets", one of which is declared to be the "default" flow
target (the only semantics associated with the default flow target is
that you will be warned whenever you are delivering to a stream that is
not marked as the default flow target for that repository workspace).
Whenever you pick a new stream as a flow target, it gets added to this
list (open up the workspace in the workspace editor, and you can view
and manipulate all of the flow targets of the workspace).
Cheers,
Geoff
tmok wrote:
You can change the flow target of a remote workspace and changes not
in the target will become outgoing change sets. You can deliver those
changes to the target (your new stream).
In Pending Changes view, right-click on your workspace and select
'Change Flow Target...' to flow your changes to the new stream.
