Subversion Best Practices: Merging and Merge Tracking |
|
|
|
|
Broadcast Date: Wednesday, January 19, 2011 Speakers:
Most enterprises find themselves with multiple lines of development in process simultaneously that need isolation. The logical way to accomplish that isolation is through branching, but the need for isolation is normally short lived before the work needs to be merged with changes made on other lines of development. That means merging. Of course you want to know what has been merged to what and you want the tool to facilitate subsequent merges by utilizing that knowledge as well. That means merge tracking. This webcast will be looking at best practices around merging and merge tracking. It will be assumed that the participant already knows what both of these features are and from a high level how Subversion logs merge tracking data. The webcast will dig deeper looking at:
CollabNet has been the primary commercial sponsor of Subversion since its inception, as well as the leader in helping enterprises deploy Subversion. This depth of experience together with the technical knowledge of the implementation of merge tracking gives CollabNet the ability to share merging best practices that have worked for other enterprises.
Bob Jenkins, Director, Subversion Services, Bob Jenkins has spent nearly 14 years focused on application life-cycle tools. For the past nine years, Mr. Jenkins has worked for CollabNet as a sales engineer, principal collaboration consultant, senior product marketing manager, and currently as Director of Subversion Services. At CollabNet, Mr. Jenkins helps define the areas of investment by CollabNet in Subversion, the fastest growing version control tool designed for software configuration management (SCM). He also consults with enterprises that are planning to adopt Subversion on how to apply best practices to their SCM processes. Mr. Jenkins has over 20 years of experience in software development and application customization. Prior to CollabNet, Mr. Jenkins worked for Rational Software concentrating on configuration and change management.
Paul joined CollabNet's Version Control/SCM Team as a developer in 2007. In that role he does open source development on the Subversion project where he is a full-committer. His initial role at CollabNet was to help complete the implementation of Subversion's merge tracking feature. His continued effort in improving the performance and functionality of merge tracking makes him an expert on this topic. Prior to working at CollabNet, Paul got his first exposure to Subversion while working to port it to IBM's OS/400 (a.k.a. i5/OS, IBM i).
|







About the Sponsor: