Managing the Streams Interface
Given that streams are presented in the Team Artifact>Streams without any hierarchy (or at least I could not create any structure), what is the approach for real-world projects with multiple concurrent release targets, code maintenances branches and technology exploration branches?
I am struggling to try to understand how to manage within a RTC project of up to 50 streams.
Or am I braking up the wrong tree and should be organizing the real world project to multiple RTC projects?
I am struggling to try to understand how to manage within a RTC project of up to 50 streams.
Or am I braking up the wrong tree and should be organizing the real world project to multiple RTC projects?
One answer
The current mechanism for managing this is to define your Team Artifact
filter to only show you objects from the team areas you are interested
in (you get to specify what team areas you are interested in). There is
also a pre-defined filter which is "just team areas that I am a member
of". Have you tried using that?
Cheers,
Geoff (ClearCase Connector team)
limwsv wrote:
filter to only show you objects from the team areas you are interested
in (you get to specify what team areas you are interested in). There is
also a pre-defined filter which is "just team areas that I am a member
of". Have you tried using that?
Cheers,
Geoff (ClearCase Connector team)
limwsv wrote:
Given that streams are presented in the Team Artifact>Streams
without any hierarchy (or at least I could not create any structure),
what is the approach for real-world projects with multiple concurrent
release targets, code maintenances branches and technology
exploration branches?
I am struggling to try to understand how to manage within a RTC
project of up to 50 streams.
Or am I braking up the wrong tree and should be organizing the real
world project to multiple RTC projects?