RTC Developers work on same stream
BedBath User (21●9●8)
| asked Jun 05 '12, 11:59 a.m.
edited Jun 07 '12, 6:43 p.m. by Geoffrey Clemm (30.1k●3●30●35)
similar to a user joining a project and creating their view to join an existing stream (so developers all work on the same stream), how do you do similar to that in RTC?
|
3 answers
Barb,
I am guessing that by "join project" and "stream" you are referring to ClearCase UCM? If so, the underlying paradigms are quite different. In RTC, a stream is actually the same object as a repository workspace, only it cannot be loaded. Hence, developers never work on a stream, they only deliver their work (from a repository workspace) to a stream, or directly to another workspace. RTC has no concept and no need of checking out sources (and no dynamic views, no version tree). Instead it uses change sets as the atoms of its versioning. The use case to have two developers work on "the same development stream" would be realized by having their workflows flow against the same stream. Use cases of stream management are detailled in library article 599 That said, with the web client you can directly access a stream (e.g. for document versioning). This is detailled in library article 361 You can find a comparison between RTC and ClearCase terms in this article. - Arne Comments 
Geoffrey Clemm
commented Jun 10 '12, 5:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that in UCM a team stream is also the same kind of object as a repository workspace (in UCM, a repository workspace is just a UCM stream). And with the standard UCM "private stream" way of working, developers never work on the team stream, they only deliver their work from their development stream to the team stream. They can do a find-merge style delivery to another development stream, but that is rarely done.
Geoffrey Clemm
commented Jun 10 '12, 5:54 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that in RTC, the "lock" command servers a similar purpose as the "reserved checkout" UCM command. RTC does have a simple version tree, available in the History View. Like RTC, UCM uses change-sets, but you cannot do all the RTC change-set operations on a UCM change-set (in particular, you cannot "suspend" it from your workspace). |
The new developer should create a repository workspace that flows with the dev stream. The easiest way to do that is to right click on the stream in the Team Artifacts view and select New > Repository Workspace.
|
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 10 '12, 5:30 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
For folks not familiar with ClearCase UCM, it provides three standard ways of working:
- shared team stream (you use dynamic views, checkin to make your changes visible on the team stream, and you see changes when they are checked in to the team stream) - semi-shared team stream (you use snapshot/web views, checkin to make your changes visible on the team stream, and you update to see changes on the team stream). - private development stream (you deliver from your development stream to make your changes visible in the team stream, and you rebase from the team stream to see changes on the team stream). RTC provides the shared and private modes ... shared team stream in web GUI, and private development stream in the non-web GUI (Eclipse, Visual Studio, command line). The primary differences are terminology: - a UCM "development stream" is called a "workspace" in RTC - a UCM "rebase" is called an "accept" in RTC - a UCM "web view" is called a "sandbox" in RTC - a UCM "checkout" is called a "lock" in RTC So to answer the question, for all developers to "work on the same stream" in RTC, you need to use the RTC web client. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.