Version control systems are essential for managing any slightly complex software project, but few teams have given much thought about how to get the most out of their repository.
The most common best practices for source control are based on the needs of shrink wrap or open source software. Running a website is different, and needs different approaches to tracking modifications.
This session will take an in-depth look at the idea of shipping trunk and branching in code. We’ve found that this technique reduces the risks associated with change, allowing you to:
We’ll discuss how (and why) you’d want to do all this, and cover some of the downsides of this technique.
The ideas discussed will be useful for both developers and operations, and will work with any revision control system from CVS to Git.
Paul Hammond is a web developer, product manager and father. He has been building websites for as long as he can remember, and now leads a team of hard-working supernerds at Flickr. Before then he was part of the Yahoo Brickhouse team, and previously led technical project management at BBC Radio and Music interactive.
Comments on this page are now closed.
For information on exhibition and sponsorship opportunities at the conference, contact Yvonne Romaine at firstname.lastname@example.org
Download the Velocity Sponsor/Exhibitor Prospectus
For media-related inquiries, contact Maureen Jennings at email@example.com
To stay abreast of conference news and to receive email notification when registration opens, please sign up for the Velocity Conference bulletin (login required)
View a complete list of Velocity contacts