Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Book Image

Visual SourceSafe 2005 Software Configuration Management in Practice

Overview of this book

Why is Software Configuration Management important?Software Configuration Management (SCM) is the discipline of managing the building and modification of software through techniques including source-code control, revision control, object-build tracking, and release construction. SCM involves identifying the configuration of the software at given points in time, systematically controlling changes to the configuration, and maintaining the integrity and traceability of the configuration throughout the software development lifecycle.Software Configuration Management is one of the first skills a serious developer should master, after becoming proficient with his or her development tools of choice. Unfortunately, this does not always happen because the subject of SCM is not commonly taught in either academic or company training.When developing software, you need to have a manageable team development effort, track and maintain the history of your projects, sustain parallel development on multiple product versions, fix bugs, and release service packs while further developing the application. This is where the concepts of Software Configuration Management come into play; SCM is about getting the job done safer, faster, and better.Visual SourceSafe has a long history behind it. The previous versions were either loved for their ease of use and integration with other Microsoft products, or hated because the headaches caused by using them improperly. This book will help you to avoid such problems.
Table of Contents (15 chapters)
Visual SourceSafe 2005 Software Configuration Management in Practice
Credits
About the Author
About the Reviewers
Preface

Parallel Product Development


After releasing a new version of the product, the development effort doesn't stop. The product will advance towards the next release while a separate effort will be made to maintain the current release and fix the issues found after the product is installed in the production environments. These efforts cannot be conducted on the same code base. They have to be conducted in parallel. This is where we introduce codelines.

Codelines

The codeline is the basic concept that represents the progression of the set of source files and other resources that make up the software product. It represents the development evolution across time, having a continuous history.

The first codeline is created when the development process is started and the initial files are added under source code management. This codeline is called the mainline or trunk.

If the mainline is used as the current development codeline it is also referred to as the development line.

In the OrbitalHotel example...