Perforce High Level Best Practices in Configuration Management高级配置管理最佳实践.pdfVIP

High-level Best Practices in SCM High-level Best Practices in Software Configuration Management Laura Wingerd Perforce Software, Inc. wingerd@ Christopher Seiwald Perforce Software, Inc. seiwald@ April 27, 1998 Abstract When deploying new SCM (software configuration management) tools, implementers sometimes focus on perfecting fine-grained activities, while unwittingly carrying forward poor, large-scale practices from their previous jobs or previous tools. The result is a well-executed blunder. This paper promotes some high-level best practices that reflect the authors’experiences in deploying SCM. 1 High-level Best Practices in SCM 1. Introduction “A tool is only as good as you use it,” the saying goes. As providers of software configuration management (SCM) tools and consultants to software companies, we are often asked for sound advice on SCM best practices – that is, how to deploy SCM software to the maximum advantage. In answering these requests we have a bounty of direct and indirect SCM experience from which to draw. The direct experience comes from having been developers and codeline managers ourselves; the indirect experience comes from customer reports of successes and failures with our product (Perforce) and other SCM tools. The table below lists six general areas of SCM deployment, and some coarse-grained best practices within each of those areas. The following chapters explain each item. Workspaces, where Don’t share wor