Home 
Resources CM Yellow Pages Articles and Whitepapers CM Crossroads Articles Experience Report: Using the Stable Receiving-Line to Support Parallel Development
Resources CM Yellow Pages Articles and Whitepapers CM Crossroads Articles Experience Report: Using the Stable Receiving-Line to Support Parallel Development
Experience Report: Using the Stable Receiving-Line to Support Parallel Development
Address
Michael Sayko mss@acm.org
By Michael Sayko
What words come to mind when you mention “parallel development” to software developers and projects managers? Complex and painful may be the typical response. Yet parallel development need not be difficult and laborious. By adopting an appropriate branching and merging strategy, parallel development can be straightforward and efficient.
The stable receiving-line, identified in Streamed Lines: Branching Patterns for Parallel Software Development, is a branching and merging strategy that is ideally suited for projects that need to support two or more releases at the same time. The primary benefit of the stable receiving line is that it isolates the development activities for each release while providing a home codeline that is always stable.
What words come to mind when you mention “parallel development” to software developers and projects managers? Complex and painful may be the typical response. Yet parallel development need not be difficult and laborious. By adopting an appropriate branching and merging strategy, parallel development can be straightforward and efficient.
The stable receiving-line, identified in Streamed Lines: Branching Patterns for Parallel Software Development, is a branching and merging strategy that is ideally suited for projects that need to support two or more releases at the same time. The primary benefit of the stable receiving line is that it isolates the development activities for each release while providing a home codeline that is always stable.
Reviews (0)
Be the first to review this listing!