Hi, |
Re: Baseline set delete Don't get too hung up on version labels - whilst it's nice to have a perfect sequence and save version 1.0 to be the first official release, it's just a version label - in your case version 2.0 might have to be the first official release. I've seen modules with version labels well beyond version 1.0 before they are identified as the first official release. You also have to be careful with deleting baselines - the version you see when you open a module is the so called "current version" - a really poor use of terminology - it is not the current or latest version, it is in actual fact a checked-out editable copy of the previous baseline plus any changes that have been made. It is essentially a draft of what will become the next baseline version. Deleting version 1.0 will have no effect on the "current version". Some users make the mistake of thinking that if you delete the previous baseline, the "current version" will change and revert back to being based on the new previous baseline. Paul Miller Melbourne, Australia |
Re: Baseline set delete SystemAdmin - Sun Aug 14 19:36:05 EDT 2011 Paul Miller Melbourne, Australia thank you Paul for your response. The 1.0 baseline set label is just closed with no files baselined so my current is still 0.5 (current) . I think I have lost this 1.0 label forever now. =( So I created a copy of the original baseline set definition and did a baseline of my modules there. The modules are individually labeled as 0.6, but the baseline set label doesn't match. It is (0.1). I guess I can use this until my 1.1 version where I can switch back. I assume there is no way to consolidate the two definitions since the original baselines didn't port over. I am confused on what are the real version? Is it the actual labels on each files and not the baseline set numbers? Should I release the baseline set by where the lastest module versions are at and not the baseline set label? example release like: /folder/module1 baseline 0.6 /folder/module2 baseline 0.6 /folder/module1 baseline 0.4 instead of baseline set 0.1 thank you for your help :) |
Re: Baseline set delete SystemAdmin - Sun Aug 14 19:36:05 EDT 2011 Paul Miller Melbourne, Australia thank you Paul for your response. The 1.0 baseline set label is just closed with no files baselined so my current is still 0.5 (current) . I think I have lost this 1.0 label forever now. =( So I created a copy of the original baseline set definition and did a baseline of my modules there. The modules are individually labeled as 0.6, but the baseline set label doesn't match. It is (0.1). I guess I can use this until my 1.1 version where I can switch back. I assume there is no way to consolidate the two definitions since the original baselines didn't port over. I am confused on what are the real version? Is it the actual labels on each files and not the baseline set numbers? Should I release the baseline set by where the lastest module versions are at and not the baseline set label? example release like: /folder/module1 baseline 0.6 /folder/module2 baseline 0.6 /folder/module3 baseline 0.4 instead of baseline set 0.1 thank you for your help :) |
Re: Baseline set delete sweet_tpie - Sun Aug 14 21:30:38 EDT 2011 I'm not sure how familiar you are with configuration management concepts but Baseline Sets are used to capture the versions of multiple modules at a distinct point in time such as projects milestones like review gates or a major delivery gate of some sort. The version label of a Baseline Set is often differant to the version labels of each of the modules that will be part of the set - for example, assume a Baseline Set that has three modules assigned to it, Module A, B and C. Prior to all modules being been rolled into a major version of this Baseline Set (lets say major version 1.0), assume that their module versions are: Module A - version 2.3 Module B - version 0.6 Module C - version 3.0 After rolling all modules into the version 1.0 Baseline Set, the module versions will all be raised to their next major version. So Baseline Set version 1.0 is comprised of the following module versions: Module A - version 3.0 Module B - version 1.0 Module C - version 4.0 If you haven't rolled any of the modules into a Baseline Set, you can back out of it by clicking on the "Close" button - a warning will pop up - just select "Yes" to back out. All that will happen here is that you will lose the version label for the Baseline Set, but the version labels of each of the modules will not be altered from what they were. Paul Miller Melbourne, Australia |