Source Code Management Basics
Download as ODP, PDF2 likes4,523 views
Source code management (SCM) is used to manage changes to source code over time. There are two main types: centralized SCMs which keep the main copy of code in one central place, and distributed SCMs which allow full copies of the code across devices. SCMs provide version control, allowing developers to check out code, make changes, and commit changes back while resolving any conflicts between versions. Common SCMs include Git, Mercurial, Subversion and Team Foundation Server.
![Source Code Management Basics Chris Tankersley E-mail: [email_address] Twitter: @dragonmantank](https://image.slidesharecdn.com/sourcecodemanagementbasics-110127094522-phpapp02/85/Source-Code-Management-Basics-1-320.jpg)
Source Code Management Basics
- 1. Source Code Management Basics Chris Tankersley E-mail: [email_address] Twitter: @dragonmantank
- 2. Who Are You and Why Are You In My House? Chris Tankersley Been doing PHP for almost 8 years now Lots of projects no one uses released under the BSD license Contributer to the Habari Project
- 3. Source Code Management Just do it
- 4. Don't use VSS or CVS
- 5. Good Night!
- 6. Questions?
- 7. Source Code Management (For Reals) Change management for source code
- 8. Easy to use
- 9. Different kinds for different problems
- 12. SCM Basics Check out the code
- 13. Modify it
- 14. Download changes
- 15. Test it
- 16. Commit it
- 17. Pick your Poison Two different kinds – Centralized and Distributed
- 18. Centralized keeps main copy in one place
- 19. Everyone has a full copy in Distributed
- 20. Centralized SCMs CVS (Don't use, it's ancient)
- 21. Subversion
- 24. Visual Source Safe (Don't use under penalty of death)
- 26. Mercurial
- 27. Bazaar
- 28. Bitkeeper
- 29. Common Vocabulary Checkout Download a copy of the source to your machine Commit Saving your changes to the SCM Repository Place where the source code is kept „ I checked out the code this morning and commited the changes back to the repository”
- 30. Demo Time!
- 31. Branching Copying the code to another section of the repository so that it doesn't interfere with other code
- 32. Like This!
- 33. Merging Taking two sets of code and making them one
- 34. Like This!
- 36. Taking it from Here Commit hooks
- 39. Questions?