Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic SYNERGY (steve huntington)
Decrease font size
Increase font size
Topic Title: Release predecessor and reconfigure process
Topic Summary:
Created On: 24-Aug-2004 16:45
Status: Read Only
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
Answer This question was answered by Stephane POLICET, on Friday, March 11, 2005 5:02 PM

Answer:
Hello,
Is it possible to define a priority between releases, that could be used in reconfigure process.

Example :
2 releases "V1" (for V1 maintenance) and "V2" (for next application version development).
object "O" has 1 version in each release :
- "OV1" created on 2003/01/01 in release "V1"
- "OV2" created on 2003/12/31 in release "V2", successor of "OV1"

In release "V1", I create another successor "OV1bis" to "OV1" on 2004/01/01. "OV1bis" and "OV2" are parallel versions in different releases.

The reconfigure properties of my V2 project are :
- a "V1" baseline
- all completed tasks in release "V1"
- all completed tasks in release "V2"

After reconfigure, I get "OV1bis" because it is newer than "OV2".

Is it possible to define that "V2" release is successor of "V1", so that if there are candidates in "V2", "V1" candidates are eliminated of reconfigure process, so I get "OV2" until "OV1bis" modifications are merged in "V2" release ?
 24-Aug-2004 16:45
User is offline View Users Profile Print this message


Stephane POLICET

Posts: 1
Joined: 24-Aug-2004

Answer Answer
Hello,
Is it possible to define a priority between releases, that could be used in reconfigure process.

Example :
2 releases "V1" (for V1 maintenance) and "V2" (for next application version development).
object "O" has 1 version in each release :
- "OV1" created on 2003/01/01 in release "V1"
- "OV2" created on 2003/12/31 in release "V2", successor of "OV1"

In release "V1", I create another successor "OV1bis" to "OV1" on 2004/01/01. "OV1bis" and "OV2" are parallel versions in different releases.

The reconfigure properties of my V2 project are :
- a "V1" baseline
- all completed tasks in release "V1"
- all completed tasks in release "V2"

After reconfigure, I get "OV1bis" because it is newer than "OV2".

Is it possible to define that "V2" release is successor of "V1", so that if there are candidates in "V2", "V1" candidates are eliminated of reconfigure process, so I get "OV2" until "OV1bis" modifications are merged in "V2" release ?
Report this to a Moderator Report this to a Moderator
 26-Aug-2004 07:18
User is offline View Users Profile Print this message


Mert Vuraldi

Posts: 22
Joined: 2-Feb-2004

Hi Stephane,

what You are looking for is perhaps task based CM with release scoring.
Take a look at TB-169 in the knowledgebase.

This method sometimes is a bit tricky and its not recommended by Telelogic,
but I worked that way once and had no special problems.
IMHO its a just bit problematic because of the break with pure task based
concept.

Anyway the point is that the system does, what You want

Regards,

Mert
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic SYNERGY forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 15:34.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.