It's all about the answers!

Ask a question

SCM Best-practice baseline and snapshots


Tom Frauenhofer (1.3k58435) | asked Sep 08 '10, 9:33 a.m.
retagged Dec 16 '13, 4:01 p.m. by David Lafreniere (4.6k7)
Most (perhaps all) development projects need to 'label' an important
configuration (say, when a product is released to users) so that
configuration can be referenced later.

We used to call these labels "tags".

To this end, my team has been promoting snapshots created by our JBE's.
It seemed natural and easy to do. We have never created baselines and
delivered them.

What are the considerations for choosing one (promoting snaphsots) over
the other (delivering baselines) ?

Is there some doc on this that I haven't seen or found ?

Any help appreciated
Dave


P.S. I can think one reason to prefer promoting snapshots ... when you
have lots of components (as we do), its seems easier. I'd have to
baseline each component separately and then deliver each baseline.

11 answers



permanent link
John Bayley (122) | answered Feb 25 '15, 4:02 p.m.
I am curious about an answer to Leonardo Marzo's question:

Very interesting thread. I have one more question. So, which are the consequences of delivering a baseline from a workspace to a stream. You are only saying "hey baseline, now you should also be visible from the component's stream node, when I click on Component--> Show baselines" ??

I must confess too, that my head hurts while trying to parse the statement:

That [reverting a component to a previous baseline] would not be easy to do with a snapshot because the snapshot's baselines aren't in the stream.

I realise that baseline creation is optional when you create a snapshot - although I'm not really sure why. However, presuming that baselines were created for a given snapshot (such as when a build runs) and that build snapshot is 'promoted' (which I believe is deprecated terminology), should the baselines not also be present/visible in the stream (or in the stream's components, to be semantic)?

Your answer


Register or to post your answer.