configuration management

Personality matters a great deal when you need to be able to help a small team implement essential software configuration management practices. Small teams have dynamics just like any other team and you need to know what it takes to help your team achieve success. SCRUMs may have a maximum size of nine members, but you will likely find yourself in organizations where successful teams grow and you have to deal with the dynamics implicit in a successful team that now has new requirements for communicating and working together successfully. In this column, we will take a look at some of the essentials required for small teams.

I am about to migrate a software library from Visual SourceSafe to Dimensions 2009R1, are there any problems I should be aware of?

I assume the best idea is to put the migrated VSS into its own product. I ask this because I also have a migration of Serena ChangeMan into the same database and I may be requested to put both migrations into the same product.

Thanks,
Stephen.

my company was recently aquried by another company. we moved all of our servers over as is. everything is working fine. now they want to add us to a new windows domain as well us upgrade us from cc 7.1.1 to 7.1.2.

is it as simple as throwing out the current views and running fix_prot on the vobs?

or is there more to it then that?

thanks for your time

The other day I came across 2 people on the same day who told me that they believe that part of the build system's job is to do software configuration management. :blink:

Having spent nearly all of my professional life in SCM this came as surprise to me because I've tried to avoid using the build system to manage software configurations, and whenever I've come across these build systems these were highly complex solutions with lots of gotchas and usually created in part from a legacy environment that used 'simple' version control tools.

Both of these people happened to be Subversion advocates and it got me wondering whether this has anything to do with the fact that Subversion was built as a replacement for CVS and doesn't have the notion of configurations.

What do you say? Is Software Configuration Management the build system's job? Or is it a shared responsibility between the SCM/VC system and the build system?