Hi,

No, not really. When we create a new stream based off a snapshot there is no ease way of finding out which snapshot you based that stream on. This is a common communication problem in our world when we talk about defects. Suppose a release is represented by a snapshot and you want all teams to adopt that snapshot as their new stream base. Now, some teams adopt that snapshot and some dont. Every team member will not be aware that their stream is updated or not because you want a single person to do the upgrade. When the team members talk with other teams there is no easy way of establishing that they are working off the same base and hence talking about the same problems.
Weve been thinking about using flow targets but streams are moving targets and maybe you dont want to flow changes in to your project stream all the time.

What were looking for is like a snapshot acting as a one way flow target. Then that stream would have a record of what its based on and it would be easy to rebase that on a new snapshot using the pending changes view (instead of using "replace with snapshot") .

-Hampus

Are you looking for something like work item 130615: "Baselines should
have a predecessor/successor graph display, including branching/merging,
similar to the current file history display"

On 12/6/2010 8:38 AM, hampus wrote:

Hi,

Is there some way of finding out which snapshot/snapshots from which
baselines derive from? I know that those baselines that were created
in the context of the snapshot will inherit the snapshot name but for
all other baselines the name is taken from the baseline or previous
snapshot.

The feature Im looking for is the traceability from a rebase of a
stream to the originating snapshot (on which the rebase is founded).


Regards,
Hampus