Component shared between two different team areas
We are thinking of following approach.
* We create a common component for this codebase and make
* Make this component part of the
Can the folks who are part of
If not, are there any other better ways to managee this requirement?
Many Thanks..
One answer
Hi:
This is a very common situation. Common component can be owned by team area "zzz". Different streams owned by different team areas "zzz", "yyy", etc. can have different versions of that common component (different baseline, different change set history).
So yes, the folks in "yyy" team area can be allowed to deliver their changes to that component in a particular stream - e.g. their development stream, owned by their team area "yyy". And your organization can even decide the folks at "yyy" should not be allowed to deliver changes to that component in a higher level stream "integration stream" - but certain members of a certain role in "xxx" should be allowed to.
The precondition "Restrict Change set delivery to components in a stream" lets you pick a stream, component(s) in that stream and the roles allowed to deliver to these components in that stream. See the example at http://jazz.net/library/article/215#componentadvisor
HTH,
Christophe Cornu
Jazz Source Control Committer
This is a very common situation. Common component can be owned by team area "zzz". Different streams owned by different team areas "zzz", "yyy", etc. can have different versions of that common component (different baseline, different change set history).
So yes, the folks in "yyy" team area can be allowed to deliver their changes to that component in a particular stream - e.g. their development stream, owned by their team area "yyy". And your organization can even decide the folks at "yyy" should not be allowed to deliver changes to that component in a higher level stream "integration stream" - but certain members of a certain role in "xxx" should be allowed to.
The precondition "Restrict Change set delivery to components in a stream" lets you pick a stream, component(s) in that stream and the roles allowed to deliver to these components in that stream. See the example at http://jazz.net/library/article/215#componentadvisor
HTH,
Christophe Cornu
Jazz Source Control Committer