SVN notes

463 views

Published on

some notes about source code version control.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
463
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

SVN notes

  1. 1. WHA T’ s theP RO B L E MS ?
  2. 2. 2 S tories……
  3. 3. S to ryN O .1
  4. 4. Releas New Releasee Feature ??
  5. 5. S to ryN O .2
  6. 6. svn repositorylibs
  7. 7. The only measure of progress is workingcode in source control.
  8. 8. If it’s not in source control, it doesn’t exist...
  9. 9. Get up-to-date before working on a file.
  10. 10. Do not commit if code doesn’t pass localtesting or won’t even compile.
  11. 11. Immediately commit after completing apiece of functionality.
  12. 12. Every committed revision gives you arollback position.
  13. 13. The risk of a merge nightmare increasesdramatically with time.
  14. 14. It forces you to isolate features intodiscrete units of work.
  15. 15. One commit for one purpose.One purpose into one commit.
  16. 16. Do not commit any artifacts auto-generated out of the building process(e.g.program binary).
  17. 17. Make sure all commit contain comments.
  18. 18. Here are some anti-patterns of good commit messages: 1. Some shit. 2. It works! 3. fix some fucking errors 4. fix 5. Fixed a little bug... 6. Updated 7. typo 8. Revision 1024!!
  19. 19. Good process:1. Get up-to-date2. Build3. Never work on broken build4. Develop5. Build6. Local testing7. Commit8. Resolve conflicts immediately9. Get up-to-date

×