 |
 |
Bibliography Successes Feedback |
Contents Search Glossary |
|
 |
||||
|
||||||||
               |
SCM Configuration Versioning
Posted by Randall Becker, Nexbridge Inc., 3-Nov-1999The question of version numbering and threading (the use of names or tags to identify "something") is closely tied to the business processes in use at your company. The rest of this is just perspective, if it helps. Version numbers, taking a broad brush view of the Universe, tend to reflect variants: The tagging or thread identification, pre-release, for example, is a moving tag identifying an anchor or reference point people can use when needing to identify what needs to be used when: a) fixing or enhancing a branch (main or otherwise); b) building part of a product. You'd need named threads where you need to explicitly select large numbers of related component versions (say, to build a subsystem). This would depend on how many support levels you'd need (prod, prod-1, prod-2, pre, etc.). Don't go wild on these because the more you have, the more you need to manage. The K.I.S.S. principle definitely applies here. If you don't need to build at anything beyond pre, you don't need threads beyond that - unless you need to fix bugs and build later on - OOPS... that's a common miss. Realistically, you can choose any model you like, but it should reflect how you do development (and that may vary from project to project/product to product). The biggest mistake I've seen people make in the CM world is to believe that putting in place CM will fix their problems. CM, when used to implement a bad process will result in bad CM - trust me on this one, I've consulted for a long time and this is a common theme. Make sure your processes are in order first. Picking a naming/numbering scheme following that should be relatively straight forward.
|
