If you want to recreate a snapshot, you would create a stream from the
snapshot itself, not from the stream that parents the snapshot. As you
pointed out; they may differ.

Generally speaking, no, you would probably not want to associate a
snapshot with a stream that is completely different. But we're not
enforcing that the snapshot/stream have to be similar in order for them to
be related.

As Geoff says, associating a snapshot allows you to easily get a list of
"snapshots for that stream". I believe I posted on another thread: imagine
if you are deleting an old stream. You might take a snapshot to back it
up. But it doesn't make sense to associate the snapshot with the stream
you intend to delete. Instead you can associated it with the current
stream. All of the content in the baselines (and the included components)
might be totally different but now you can delete the old stream knowing
you have a snapshot to resurrect it if you need to.


On Fri, 04 Dec 2009 00:38:18 -0500, Chemi <jmordax> wrote:

On 04-Dec-09 6:30 AM, Geoffrey Clemm wrote:
The primary purpose for associating a snapshot with a stream is so that
the snapshot appears in the list of "snapshots for that stream" (that
you can get from the GUI).

Cheers,
Geoff

Right, but if I try to recreate that promoted snapshot from that "new"
stream in my workspace I understand it will fail because the "new"
stream doesn't contain the right baselines of the components. What is
more... it is possible that not all components have been add to it.

So I don't understand why I should want to associate a snapshot with a
stream if that association doesn't move/deliver/add what the snapshot
represents. I think I am misunderstanding something here... :-(

Thanks,

Chemi.

--