Open baseline without specifying suffix

Hello,

I have about 50 modules and each of these have different suffix for the baselines. I wanted to open each of these modules' baselines 1.0 and count the num of req present but because the suffix is different, I am not able to load the baseline. I have written the following code.

{ c o d e }
Item itm
Folder fol = current
Module mod
Object obj
int cnt = 0
for itm in fol do
{
if( type(itm) == "Formal" )
{
mod = read( fullName(itm), true)
print name(itm) "\t"
b = baseline(1,0,"")

load(mod, b, true)
for obj in mod1 do
{
cnt++
}
print cnt "\n"
}
}
{ c o d e }

Any help to open a baseline with out specifying the suffix?

Thanks
JSN
jnbharadhwaj - Tue Aug 14 03:10:57 EDT 2012

Re: Open baseline without specifying suffix
llandale - Tue Aug 14 13:47:26 EDT 2012

Use {code} not { c o d e }

Do you want the LAST baseline 1.0 suffix? e.g. want "1.0(c)" when exists 1.0(a) and 1.0(c)?
You could loop through the baselines, stop when you have seen a 1.0 but the current one is no longer 1.0; and use the previous baseline. 

Baseline bl
bool Found10 = false, Is10
string Suffix10 = ""
for bl in mod do
{  Get major/minor/suffix
   Is10 = major/minor are 1/0
   if (Found10 and !Is10) break     // e.g. baseline 1.1 or 2.0
   if (Is10) SuffixLast = suffix
}
if (!Found10) then no such 1.0 baseline at all
elseif(null SuffixLast) then the single 1.0 has no suffixes
else use 1.0(SuffixLast)


-Louie

Re: Open baseline without specifying suffix
jnbharadhwaj - Mon Aug 20 23:38:06 EDT 2012

Hello,

I tried this and it worked fine. Thank you for the help.
Have a great day!

JSN

Re: Open baseline without specifying suffix
Tony_Goodman - Mon Oct 01 07:30:04 EDT 2012

jnbharadhwaj - Mon Aug 20 23:38:06 EDT 2012
Hello,

I tried this and it worked fine. Thank you for the help.
Have a great day!

JSN

Since when have you been able to create a new baseline with the same number as the current baseline, but with a different suffix?

I don't how I missed this!

Must be getting old :-(

Tony Goodman, www.smartdxl.com

Re: Open baseline without specifying suffix
SystemAdmin - Mon Oct 01 18:02:25 EDT 2012

Tony_Goodman - Mon Oct 01 07:30:04 EDT 2012
Since when have you been able to create a new baseline with the same number as the current baseline, but with a different suffix?

I don't how I missed this!

Must be getting old :-(

Tony Goodman, www.smartdxl.com

Tony - DOORS has been able to do this since at least DOORS 5.x possibly earlier, I go as far back as DOORS 3.x but can't recall that far back.

The configuration management convention for version & baseline labeling is that each label must be unique - noting that DOORS refers to a conventional version as being a "Baseline" and a conventional baseline as being a "Baseline Set" - so I guess DOORS technically honors this label uniqueness by allowing versions to have the same Major.Minor number but with different suffixes.

Despite this, I'm pretty sure that it's widely accepted that it's good practice for the Major or Minor numbers to be always incremented on each version check-in which is enforced in many Configuration Management tools.

Paul Miller,
Melbourne, Australia

Re: Open baseline without specifying suffix
llandale - Tue Oct 02 17:21:03 EDT 2012

Tony_Goodman - Mon Oct 01 07:30:04 EDT 2012
Since when have you been able to create a new baseline with the same number as the current baseline, but with a different suffix?

I don't how I missed this!

Must be getting old :-(

Tony Goodman, www.smartdxl.com

The inserted that capability at the same time as the introduced keyword "elseif" having the meaning "else if". lol

Re: Open baseline without specifying suffix
llandale - Tue Oct 02 17:28:44 EDT 2012

SystemAdmin - Mon Oct 01 18:02:25 EDT 2012
Tony - DOORS has been able to do this since at least DOORS 5.x possibly earlier, I go as far back as DOORS 3.x but can't recall that far back.

The configuration management convention for version & baseline labeling is that each label must be unique - noting that DOORS refers to a conventional version as being a "Baseline" and a conventional baseline as being a "Baseline Set" - so I guess DOORS technically honors this label uniqueness by allowing versions to have the same Major.Minor number but with different suffixes.

Despite this, I'm pretty sure that it's widely accepted that it's good practice for the Major or Minor numbers to be always incremented on each version check-in which is enforced in many Configuration Management tools.

Paul Miller,
Melbourne, Australia

Not sure what the suffix would be for if NOT to allow different baselines to have the same major.minor designations.

I wish they would enforce that the next suffix of the same major.minor MUST be alphebetically larger than the current, to stop folks from creating these baselines:
  1. 4.3(a)
  2. 4.3(c)
  3. 4.3(b)
Saw that once but lost the argument.

I can see where official releases should tend to be at a new major.minor, but the suffix system does allow for additional information; Baseline "4.3 (a)" is what "4.3" should have been, but we corrected a small bug.

-Louie