SCM: are we in a paradise now?
Hi
After reading this article "Multiple Stream Development" https://jazz.net/library/article/40, before I do some real experiments, I am surprised with the power of RTC, comparing to the old fashion ClearCase. Seems now we can do anything we like, such as: 1. We can insert any number of streams in the middle of stream hierarchy. 2. There is no fixed relationship between streams. We can deliver stuffs from any stream to another, by just changing the Flow Target. Can't imagine how to find a particular deliver in the past. 3. We can remove/add components from any stream at anytime. WOW, track the changes can be fun. 4. What else, I can feel there is a lot I don't know :+) Do we have more detailed implementation documents regarding RTC parallel development, stream strategies, etc.? On how to implement e.g. a mainline approach in RTC? Or no need strategies anymore, since we can do anything at anytime, whatever we want? Thanks Jirong |
6 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Jun 30 '11, 2:30 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Yes, with RTC you can do all of those things.
Note that by appropriate config-spec magic, you can do most of these kinds of things in base ClearCase (not with UCM though), but you had to do the config-spec magic yourself, while with RTC, it comes out-of-the-box with a GUI. WRT finding a particular deliver in the past, you can use the SCM search to find a particular change set, or you can browse the history of the stream/workspace. Cheers, Geoff On 6/28/2011 9:38 PM, hujirong wrote: Hi |
|
Thanks for your reply.
So do we still need a good stream strategy? Especially do we still need the mainline approach? Or we can now use the cascading approach or any way as we want since there is no limitation anymore. As an experienced ClearCase admin, I can smell the problems here. For newbies, this freedom can soon lead to a nightmare. Is there any other best practice or pattern documents has been written for RTC? Thanks Jirong |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 05 '11, 8:04 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
In RTC, there no technical (or other) constraints that would motivate
you to use the mainline approach over the cascading approach (from RTC's point of view, there is no different between those two approaches). So I would say that yes, you are now in paradise (:-), and you do not have to have a steam strategy (in the "mainline vs. cascade" sense), but rather just create a stream on demand when you need it (and delete a stream when you no longer need it). This will keep your stream structure as simple as possible while meeting your parallel development needs. You will want to have some stream naming conventions, so the organization gets a clue from the stream name what it is being used for (and you can rename streams at will, so you can evolve that stream naming convention over time). Cheers, Geoff On 7/4/2011 5:38 PM, hujirong wrote: Thanks for your reply. |
|
I am just about to create the first project for a large application cluster. More questions:
1. In terms of number of components required for an application/project, can we use the same knowledge we learned from ClearCase UCM? I assume they are exactly same concept. 2. In term of baseline management, is it same concept as UCM? Can we create a composite baseline at stream (has multiple components) level? Otherwise how do we release? Thank you very much for your help, Geoff. Jirong |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 19 '11, 6:20 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
1. Yes, you can use the same principles you've used for grouping files
into UCM components to decide how to cluster files into RTC components. 2. In RTC, a composite baseline is called a "snapshot". Cheers, Geoff On 7/19/2011 12:53 PM, hujirong wrote: I am just about to create the first project for a large application |
> After reading this article "Multiple Stream Development"
And when you decide to go further, you can also have a look at the article "How to keep your streams flowing smoothly in Rational Team Concert 3.0.1" at https://jazz.net/library/article/649 . This illustrates the most recent good practices for managing multiple streams efficiently. Cheers, Christophe |
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.