![]() |
Telelogic SYNERGY (steve huntington) | ![]() |
Topic Title: How to flush obsolete baselines Topic Summary: Created On: 4-May-2004 20:41 Status: Read Only |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() Answer: While developing a particular release, we typically integrate, test and create a new baseline several times a week, often every day. After 18 months and three major releases, the project history is cluttered with daily baselines and associated projects in integrate state. The vast majority of these baseline are no longer relevant. I would like to collapse a majority of these baseline projects (anything between released baselines) and flush the baselines themselves. Is there a recommended process for doing this? | |
![]() |
|
While developing a particular release, we typically integrate, test and create a new baseline several times a week, often every day. After 18 months and three major releases, the project history is cluttered with daily baselines and associated projects in integrate state. The vast majority of these baseline are no longer relevant.
I would like to collapse a majority of these baseline projects (anything between released baselines) and flush the baselines themselves. Is there a recommended process for doing this? |
|
![]() |
|
![]() |
|
I believe the recommended tool for doing this is "Save Offline and Delete" (in v6.3).
There are even a couple of predefined scopes just for the purpose of removing Baselines and the assocaited projects. You'll find the feature under the Tools menu in the "old" client. You must have the ccm_admin role to delete static objects. |
|
![]() |
Telelogic SYNERGY
» SYNERGY/CM
»
How to flush obsolete baselines
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.