7. Making the Switch to DVCS
How Atlassian teams moved from centralised to
distributed version control
John Stevenson, UK Ambassador, Atlassian
7
Friday, April 20, 12
33. Distributed Version Control
Git or Mercurial
Git or Mercurial Git or Mercurial
Git or Mercurial
Git or Mercurial Git or Mercurial
Friday, April 20, 12
40. Not just the command line
The command line is like Marmite...
Friday, April 20, 12
41. “ Distributed Version Control is flexible and can fit any
”
workflow - you can even treat it like Subversion.
Friday, April 20, 12
42. “ Distributed Version Control is flexible and can fit any
”
workflow - you can even treat it like Subversion.
Steve Streeting
Creator of SourceTree
Friday, April 20, 12
55. Continuous Integration and
release management
• Run same builds against old
and new VCS
• Continuous Validation
• Separate repos for integration
Friday, April 20, 12
56. Continuous Integration and
release management
• Run same builds against old
and new VCS
• Continuous Validation
• Separate repos for integration
Friday, April 20, 12
74. Benefit: Developer Speed
• Common commands, just faster
• Fast tools = happy developers
• Complete history at hand
Friday, April 20, 12
75. Benefit: Developer Speed
• Common commands, just faster
• Fast tools = happy developers
• Complete history at hand
Friday, April 20, 12
76. Benefit: Fast Feedback
• More lessons learnt
• Issues resolved more timely
• Less risk and impact to a project
• More in tune with customers
Friday, April 20, 12
77. Benefit: Fast Feedback
• More lessons learnt
• Issues resolved more timely
• Less risk and impact to a project
• More in tune with customers
Friday, April 20, 12
