Create from GC new baselines, including EWM - missing command "Create new baselines, even for unchanged components"

thanks for checking may request. Only i can not agree with your conclusion.

Possible you can help me with the right OSLC specification:

is it: to create always sub configuration with the same name even if not needed, cause of no change to the baseline before?

or is it: to reuse existing baselines in sub configuration, if there are no changes?

The first option is used in GC baselines and the local configurations in ERM and ETM

The second is used for GC baselines with local configuration in EWM SCM.

This request/idea is just to harmonize the behavior.

If the requested function to not goin common with the OSLC GC specification, the existingbehaviaor also can not go with the OSLC specification.

Further more the request is to have this only optional and this function exists already in EWM SCM, it just needs to added to the GC command.

Please can you rethink about this request.

thanks

Thank you for submitting the request for an option to create a snapshot for local configurations when creating baselines in GC.

Unfortunately this would require GCM to perform actions that do not conform with the OSLC specification, and force GCM to incorporate vendor- and product-specific behavior. This would create circular dependencies and introduce non-standard OSLC behavior. For these reasons the RFE is being rejected. The best way to gain this behavior would be to request an OSLC specification enhancement that would describe a way for vendor specific behavior to be executable by OSLC CM providers. Once the change is made to the OSLC specification, GCM could incorporate the new standards into the server. To get started on a request, contact the OSLC group at http://www.oasis-oslc.org/contact or discuss this with one of your IBM representatives.

Thank you for submitting the request for an option to create a snapshot for local configurations when creating baselines in GC. Unfortunately this would require GCM to perform actions that do not conform with the OSLC specification, and force GCM to incorporate vendor- and product-specific behavior. This would create circular dependencies and introduce non-standard OSLC behavior. For these reasons the RFC is being reject.

The best way to gain this behavior would be to request an OSLC specification enhancement that would describe a way for vendor specific behavior to be executable by OSLC CM providers. Once the change is made to the OSLC specification, GCM could incorporate the new standards into the server. To get started on a request, contact the OSLC group at http://www.oasis-oslc.org/contact or discuss this with one of your IBM representatives.

IBM_Engineering_Offering_Mgr (IBM)
Thanks for your recommendation. In order to clarify what you're asking for, could you please provide information on the questions below? Thank you.

1. Do you want new baselines down the entire hierarchy, just for the SCM components, or something selective? In reading "This has the effect, if created a baselines from the top level in GC all global and local components get a new baseline", I think the a was intended to be all, which seems to imply the former.

answer-> i wan tto create a global and local Basleiens cross all confivurations listed in this GC stream.

2. If we used differently named baselines for the same component version, you'd end up with baselines with identical content but different names based on where they're used. Is this your intent?

answer-> i want to have clear nameing concept: same name for all baselines: GC baseline name = all local baseline names

3. By "baseline", are you referring to an SCM snapshot, which is a collection of SCM baselines? The terminology is a little confusing here between OSLC and EWM SCM, but basically GCM "sees" the SCM snapshot as the contribution, which may itself have nested contributions (baselines). The naming of EWM SCM snapshot isn't under GCM control.

answer-> i'm sorry that the vendor uses different naming confention cross his tool chain and offer different behaviors of the local configurations in the GC context.

answer-> i want to select in GC an stream.

In this stream there are local streams, DNG ETM and EWM SCM streams. The EWM SCM streams have more then one Components.

Starting from the GC stream i want to create a GC baseline. This GC Baseline creates automatically baselines on all of the local streams.

This works fine for DNG and ETM, cause there is the setting: one component = one stream
and the baseline is alwas created, even if there is no change in content to the latest baseline before.

But in EWM the behavior is different: there is first a EWM stream including more than one component, which leads to two options: create a single baselien for each component or creating a snaphot and create baselines for all components inside.

addionally the not always a new baseline is created, cause EWM looks if there is a change in content to the latest existing baseline and if not the new baselien is not created, just a reference to the latest before.

But this leads to a confusing naming structure: on all components cross all applicaion the name of the created baselines are the same, exept sometimes in EWM an old baseline is used.

I want , if i create a GC baseline, that always also the EWM componets get a new baseline. Just simialr to all the other applications

If this solved via the existing opion on create a snapshot or different, this is your solution area.

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - ELM Common Services
Component - Global Configuration Management
Operating system - Multiple
Source - None

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Workflow Management (formerly Rational Team Concert- RTC)
Component - Source Control
Operating system - Multiple
Source - None

Due to processing by IBM, this request was reassigned to have the following updated attributes:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - ELM Common Services
Component - Global Configuration Management
Operating system - Multiple
Source - None

For recording keeping, the previous attributes were:
Brand - Internet of Things
Product family - Engineering Lifecycle Management (ELM)
Product - IBM Engineering Workflow Management (formerly Rational Team Concert- RTC)
Component - Source Control
Operating system - Multiple
Source - None