what pattern should we use to create new streams?
Can we create sub-stream, like a stream tree? and how it works?
for example, we have two team working on the same project, but different release versions, so we want to create two sub stream for each team, or we want to create a sub-stream for bug fix,
is there any pattern we can follow to manage the multiple streams? thanks.
for example, we have two team working on the same project, but different release versions, so we want to create two sub stream for each team, or we want to create a sub-stream for bug fix,
is there any pattern we can follow to manage the multiple streams? thanks.
2 answers
If you want it that way and it makes sense then do it. The real question you have to ask yourself is if you want the teams to be isolated from each other during development. They can use one stream but a team can potentially deliver code breakages unknowingly if they don't load the other team's code. If they use separate streams, they can coordinate an adoption while keeping an integration stream green.
There are a couple of Library articles. I'll add reference in no particular order:
How to keep your streams flowing smoothly in Rational Team Concert 3.0.1
How to manage product development using Rational Team Concert
How to keep your streams flowing smoothly in Rational Team Concert 3.0.1
How to manage product development using Rational Team Concert