It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,854

question asked: Jul 23 '09, 3:28 p.m.
question was seen: 4,364 times
last updated: Dec 20 '13, 2:03 p.m.

Related questions

Composite baselines - multiple versions of a library

0
Frank Schophuizen (193●2●32●26) | asked Jul 23 '09, 3:28 p.m.
Here is a CM scenario that I have been struggling with for many years. In words:

Does RTC support baselining a component tree containing different versions of the same component?

Explanation:
Suppose we have a system composed of components that use external components as follows: 

System X

 |-- Component A

 |     |-- using Framework XYZ123 version 1.2

 |-- Component B

 |     |-- using Framework XYZ123 version 1.2

 |-- ... and much more ...


Framework XYZ123 is a component from an external supplier.

Now Component A needs new functionality of Framework XYZ123 version 2.0, but Component B cannot be upgraded because it interfaces with other external systems that do not support Framework XYZ123 version 2.0. However, Component B needs to upgrade to version 1.3 for bugfixes.

So how can we baseline this in RTC: 

System X

 |-- Component A

 |     |-- using Framework XYZ123 version 2.0

 |-- Component B

 |     |-- using Framework XYZ123 version 1.3

 |-- ... and much more ...


In UCM it is impossible to make a composite baseline hierarchy that contains different versions of the same component. In Synergy (formerly Telelogic Synergy CM) it is possible, and we make use of this capability in our organization.

How does RTC support this?

Accepted answer

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 23 '09, 6:12 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Note that RTC lets you load multiple repository workspaces into the same
Eclipse workspace. So you can have one repository workspace with the
XYZ123 2.0 baseline, and another repository workspace with the XYZ123
1.3 baseline, and load them both into the same Eclipse workspace.
So depending on your use cases, this might be sufficient.

And one more question:
5: when you deliver a change-set that modifies some files in that
component, does that change-set get applied to both baselines, or just
one? And if just one, which one?

Cheers,
Geoff

Geoffrey Clemm wrote:
Hi Frank,

The short answer is no.

We can submit an RFE, but would need to know what semantics you
require/expect. In particular:
1: when you ask for that component to be loaded into the file system,
which baseline do you expect to be loaded?
2: if you want both baselines to be loaded into the file system, where
do you want them to be loaded?
3: when you accept a component into a workspace, which baseline do you
expect to be accepted?
4: when you deliver a new baseline of that component to a stream, does
it get added as a "third" baseline, or does it replace one of the
existing baselines (and if so, which one)?

Cheers,
Geoff


fschop wrote:
Here is a CM scenario that I have been struggling with for many years.
In words:

Does RTC support baselining a component tree containing
different versions of the same component?

Explanation:
Suppose we have a system composed of components that use external
components as follows:

System X
|-- Component A
| |-- using Framework XYZ123 version 1.2
|-- Component B
| |-- using Framework XYZ123 version 1.2
|-- ... and much more ...


Framework XYZ123 is a component from an external supplier.

Now Component A needs new functionality of Framework XYZ123 version
2.0, but Component B cannot be upgraded because it interfaces with
other external systems that do not support Framework XYZ123 version
2.0. However, Component B needs to upgrade to version 1.3 for
bugfixes.

So how can we baseline this in RTC:

System X
|-- Component A
|     |-- using Framework XYZ123 version 2.0
|-- Component B
|     |-- using Framework XYZ123 version 1.3
|-- ... and much more ...


In UCM it is impossible to make a composite baseline hierarchy that
contains different versions of the same component. In Synergy
(formerly Telelogic Synergy CM) it is possible, and we make use of
this capability in our organization.

How does RTC support this?
Frank Schophuizen selected this answer as the correct answer

One other answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Geoffrey Clemm (30.1k●3●30●35) | answered Jul 23 '09, 6:04 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Frank,

The short answer is no.

We can submit an RFE, but would need to know what semantics you
require/expect. In particular:
1: when you ask for that component to be loaded into the file system,
which baseline do you expect to be loaded?
2: if you want both baselines to be loaded into the file system, where
do you want them to be loaded?
3: when you accept a component into a workspace, which baseline do you
expect to be accepted?
4: when you deliver a new baseline of that component to a stream, does
it get added as a "third" baseline, or does it replace one of the
existing baselines (and if so, which one)?

Cheers,
Geoff


fschop wrote:
Here is a CM scenario that I have been struggling with for many years.
In words:

Does RTC support baselining a component tree containing
different versions of the same component?

Explanation:
Suppose we have a system composed of components that use external
components as follows:

System X
|-- Component A
| |-- using Framework XYZ123 version 1.2
|-- Component B
| |-- using Framework XYZ123 version 1.2
|-- ... and much more ...


Framework XYZ123 is a component from an external supplier.

Now Component A needs new functionality of Framework XYZ123 version
2.0, but Component B cannot be upgraded because it interfaces with
other external systems that do not support Framework XYZ123 version
2.0. However, Component B needs to upgrade to version 1.3 for
bugfixes.

So how can we baseline this in RTC:

System X
|-- Component A
|     |-- using Framework XYZ123 version 2.0
|-- Component B
|     |-- using Framework XYZ123 version 1.3
|-- ... and much more ...


In UCM it is impossible to make a composite baseline hierarchy that
contains different versions of the same component. In Synergy
(formerly Telelogic Synergy CM) it is possible, and we make use of
this capability in our organization.

How does RTC support this?
Comments
Frank Schophuizen commented Dec 20 '13, 2:03 p.m.

Thanks. This answers my question.

And for change to those 2 components: only one of them should be modifiable. All other should be read-only, i.e. a baselined version. 

Your answer

Register or to post 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.