Aspect-Oriented CM - if requirements (use-cases), design (models), and coding artifacts all end-up in the same repository, or at least in the same integrated CM system, there will be a desire to apply basic common policies across the board with some activity/artifact-specific tailoring.
- "Aspects" are crosscutting concerns of a system (e.g. examples may be logging and security). And since CM is a cross-cutting, integral part of a project's architecture, communication, and organization, SCM policies and practices could be automated with aspect-oriented technologies.
- AOP concepts and technologies  allow a single set of concerns/policies to be applied across all parts of the lifecycle with activity/artifact-specific tailoring ("advice") to be customer-configured and applied at the points of policy instantiation ("pointcuts"). This would facilitate policy-based and rule-based CM practices and business/workflow process enactment 
This has just been a brief taste of some of the issues. Hopefully it has provided food for thought, and as mentioned at the start, let us know what you would like to see covered in future columns.
References and Additional Resources
 Introduction to Container Based Software Configuration Management ; by Hans Thelosen, March 2002
 Flexible Component-based SCM ; by Tom Brett; BSC CMSG 2004; ( http://www.bcs-cmsg.org.uk/events/e20040317/Brett%20Flexible%20Configuration%20Management.pdf)
 SCM Patterns: Building on 'Task-Level Commit' ; by Austin Hastings; CM Crossroads Journal, June 2004
 Codeline Merging and Locking: Continuous Update and Two-Phased Commits ; by Brad Appleton et.al,CM Crossroads Journal, November 2003
 A State-of-the-Art Survey on Software Merging ; Tom Mens
 The Shlemiel way of software? Interview with Joel Spolsky for Salon Magazine
 Continuous Coordination: A New Paradigm for Collaborative Software Engineering Tools ; by Andre van der Hoek et.al; available from the "Palantir" project
 Building Collaboration into IDEs [be sure to check out the RESOURCES section of this one] ( http://www.acmqueue.org/modules.php?name=Content&pa=showpage&pid=104&page=1)
 Breaking The Code: Moving Between Private & Public Work In Collaborative Software Development ; by David Redmiles et.al; ICSGW 2003
 Tactical Approaches for Alleviating Distance in Global Software Development ; by Erran Carmel and Ritu Agarwal; IEEE Software, March/April 2001
 Unifying Artifacts & Activities visually for distributed software development teams ; Jon Froehlich et.al.; ICSE 2004
 A Weakly Constrained Approach To Software Change Coordination; by Ciaran O'Reilly; ICSE 2004
 The Agile Difference for SCM ; CM Crossroads Journal Oct 2004
 "Stellation" subproject of Eclipse
 Chianti: A tool for change impact analysis of Java Programs ; by Xiaoxia Ren et.al. OOPSLA 2004
 The Past, Present, and Future of Configuration Management ; Susan A. Dart
 Release Management ? Making it Lean and Agile ; by Robert Cowham et.al., CM Crossroads Journal, November 2003
 Continuous Staging: Scaling Continuous Integration to Multiple Component Teams ; by Brad Appleton et.al; CM Crossroads Journal, August 2004
 Streamed Lines: Branching Patterns for Parallel Software Development ; by Brad Appleton et.al.; 1998 Pattern Languages of Program Design
 Software Factories: Assembling Applications with Patterns, Models, Frameworks, and Tools ; Jack Greenfield et.al; John Wiley & Sons, 2004. See related articles:
-  System Modeling Resurrected , Andre van der Hoek, et.al.
 Aspect-Oriented Software Development with Use Cases ; Ivar Jacobson, Pan-Wei Ng; Addison-Wesley, 2005 (see http://www.awprofessional.com/content/images/0321268881/samplechapter/jacobson_ch11.pdf)
 Aspect-Oriented Software Development ; Robert Filman et.al.; Addison-Wesley, 2005
 Dissecting CM Policies , Andre van der Hoek, et.al.
 A Testbed for Configuration Management Policy Programming , Andre van der Hoek, et.al.
 A Generic, Reusable Repository for Configuration Management Policy Programming , Andre van der Hoek, et.al.