Managing Vendor Code Customizations with Stream-based SCM

Why Streams Are Easier than Traditional Branches
Member Submitted

Customizing or extending third-party "vendor" source code is becoming increasingly common especially with the availability of open source software. Managing the incorporation of vendor releases alongside customizations requires an additional layer of configuration management. Traditional branch-based software configuration management (SCM) tools require an unnecessarily complex branch and merge process. This article describes a more intuitive and efficient parallel development model for managing customizations to vendor code.

About the author

David Thomas's picture David Thomas

David Thomas is a senior sales engineer at AccuRev. Prior to joining AccuRev, David was a senior software engineer at where he successfully implemented AccuRev for an effective best-of-breed application lifecycle management (ALM) solution. Since 1996, David has been a programmer for many large Internet eCommerce Web sites where he has used numerous commercial and open source SCM tools. He holds a B.S. in Computer Science and Mathematics from the Illinois Institute of Technology.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!