Making the switch to DVCS

6,984 views

Published on

Atlassian shares their experience how we switched to distributed version control. He

Published in: Technology
  • Be the first to comment

Making the switch to DVCS

  1. Making the Switch to DVCSAtlassians move from centralized to distributedSven Peters, Ambassador, Atlassian 2
  2. DVCS @ Unite
  3. DVCS @ Unite Issue Tracker
  4. DVCS @ Unite Content Collaboration
  5. build it check get? in Task write code
  6. What is version control?
  7. What is version control? Collaboration History Copies /Branches
  8. The Past
  9. Centralized Version Control Subversion server
  10. Centralized Version Control Subversion
  11. “ Have you ever tried to merge a branch back into the trunk with SVN? Need I say more. ”
  12. Merge Time
  13. The Present (and future)
  14. Distributed Version Control
  15. Distributed Version Control Git or Mercurial Git or Mercurial Git or Mercurial Git or Mercurial Git or Mercurial Git or Mercurial
  16. “ Distributed Version Control is flexible and can fit any workflow - you can even treat it like Subversion. ” Steve Streeting Inventor of SourceTree
  17. New idea? 1997 co-op
  18. New idea? 2001 arch
  19. New idea? 2003 monotone
  20. New idea? 2003 svk
  21. New idea? 2003 darcs
  22. New idea? 2005 bazaar
  23. New idea? 2005 mercurial
  24. New idea? 2005 git
  25. New idea? 2007 iPhone
  26. Notice a Trend
  27. Notice a Trend
  28. DVCS @ Atlassian
  29. Why?Development Workflow
  30. More Why’s?Code without Limitations Dev Speed
  31. Dev Speed
  32. View File History
  33. View Authors/Blame
  34. Creating Branches
  35. Speed is power git rm hg blame hg clone git show git mvhg revert git log hg movehg pull -update git status
  36. Speed is power git rm hg blame hg clone git show git mvhg revert git log hg movehg pull -update git status
  37. Commit Often
  38. No Servers
  39. Dev Speed
  40. Code without Limitations
  41. No Servers
  42. Branching & Merging $ svn merge
  43. Don‘t be afraid
  44. Protips• DVCS Knowledge• Follow the Recipe• CI is your friend
  45. DVCS Knowledge
  46. Make use of Guru
  47. DVCS Client Git and Mercurial Mac Client
  48. FishEye - VCS to DVCS• See commits in SVN & DVCS• Browse source in any VCS Subversion, Git, Hg, CVS, P4 Browse and Search source across any VCS
  49. Follow the Recipe
  50. Bring your History
  51. Tool Integration { }
  52. Replicate Team Process
  53. Incremental Steps
  54. Continuous Integrationis your friend• Vital part of dev cycle• Run same builds against old and new VCS• Continuous Validation
  55. Make the Switch• DVCS has great business and technical benefits• Atlassian is shaping the future of DVCS
  56. Learn More & Have a Playhttp://blogs.atlassian.com/tag/switch_dvcs/http://answers.atlassian.com
  57. @svenpetsvenpet.com Thank You

×