Use case:
in My teamforge project I develop several software components, and for every component release I create a baseline which contains only the data for this specific release.
I want now to create an integration baseline which contains specific component baselines.
But teamforge doesn't allow to add sub-baselines from the own project. I can only add "External Baselines" from other projects.
Requirement:
When I create a baseline, it shall be possible to select sub-baselines from the own project.
by: Rudolf W. | over a year ago | Baselines
Comments
With regards to "For every component release I create a baseline...", are all these baselines for different components created at the same time or at different junctures?
Has the team explored the option of creating a baseline definition encompassing all the required components and related filters and then creating an integration baseline using that definition?
Hello Govind
let me explain the use case a bit more detailed:
Use case:
The team develops in one teamforge project several software components, lets say CompA, CompB, CompC.
For every development or fix they create a baseline which contains only the data of the specific component,
e.g. BL_CompA_01, BL_CompA_02, BL_CompA_03, BL_CompB_01, BL_CompB_02, BL_CompB_03, ...
Some of the consumer projects take the baselines one by one, but especially when we have many components, the project team needs to provide a validated integration of all the components.
Finally they shall provide a baseline which contains the components,
e.g. BL_INT_01 contains BL_CompA_01, BL_CompB_03, BL_CompC_02
The team cannot create the BL_INT_01 with a baseline definition, because the document versions might have evolved. BL_INT_01 must contain exactly the content of the component baselines, and the component names shall also be visible.
As a solution of this problem I only see "sub baselines"