It's all about the answers!

Ask a question

best practices for creating baselines

Marinept Villalobos (472131) | asked Apr 05 '16, 10:57 a.m.

I would like to know which could be the best practice for generating baselines. For example we usually make baselines each time that we have to deliver something for testing or when it's time to release something, instead of deliver change sets.
Some people says that its better to make a baseline after a stable version in the productive environment.

I would appeciate your opinions on the matter.



3 answers

permanent link
Gustavo Reis (13927) | answered Apr 05 '16, 1:27 p.m.
From RUP:

One distinction that needs to be made at the time of creating a baseline are whether you will be creating:
  • A 'Subsystem Baseline' with ALL the versions of files and directories that have been modified in the subsystem or subsystems.
  • A 'System Baseline' with a SINGLE version of all files and directories in all subsystems.
As a general guideline, it would facilitate release management to create System Baselines at the major and minor project milestones, and Subsystem Baselines as required or at a higher frequency. As a 'rule of thumb' it is a good idea to create a baseline if up 30% of the elements in a subsystem have been changed.

Geoffrey Clemm commented Apr 09 '16, 2:30 p.m. | edited Apr 09 '16, 2:31 p.m.

Do you you a reference for where this distinction is made in RUP?   In particular, as the term is used within the CLM products, a baseline always what is defined as a "System Baseline" above, and never is defined as "all the files that have been modified" ... that would be considered a "change set", not a "baseline".

permanent link
Arun K Sriramaiah (3.2k13077) | answered Apr 06 '16, 3:06 a.m.
edited Apr 06 '16, 3:11 a.m.
Hi Marinept,

In addition to the above, if you want to record as milestone and label ( for consolidated configuration changes) for specific reason or if its completion of consolidated configuration changes work can be labeled using baseline.


permanent link
Geoffrey Clemm (30.1k33035) | answered Apr 09 '16, 2:26 p.m.
The simplest guideline is to create a snapshot/baseline whenever you have a configuration that you might want to reference in the future, because snapshots and baselines are very cheap (to create and store) in RTC.   For example, team builds will commonly automatically create a snapshot, so that the configuration that was built can easily be referenced.

Your answer

Register or to post your answer.