Configuration management is a supporting discipline that should help assuring integrity of project items. It consists of:
- configuration management (CM) system (aka versioning systems)
You should name project documents using specific formula:
- CLX_EBanking_USM_4_1_0.docx (user manual for project CLX_EBanking, version 4.1.0).
- Vibe_ICR_SR_working.xls (working version of the status report in project Vibe_ICR).
- Never use Czech or other diacritical characters.
Never use spaces, commas and other special characters.
Separator is the underscore ("_") character.
File and directory names should not be unnecessarily long.
Use subdirectory _Archive for obsolete and archive versions.
All sensitive and formal project information should be saved only in defined locations, see below the explanation:
TYPE2 has following meaning:
Versions and versioning systems
We do not define exact form of versioning, just keep in mind that you should be able to distinguish between different versions of items. Possible forms are:
- by a timestamp in ISO format (e.g. 20120207)
- by a version number (e.g. v1_0_0 or simply 4_1_2)
- key word “working” for actual version
Versioning of source code in different systems (e.g. Subversion, TFS) should follow technology standards.
Baseline is an approved snapshot of a system (most frequently release) in a defined time. The baselined system consists of configuration items (e.g. binaries, documents, etc.).
- never change baseline once it is sent or approved by a customer
- keep the rules for versioning