SVN notes

  • 287 views
Uploaded on

some notes about source code version control.

some notes about source code version control.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
287
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
5
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. WHA T’ s theP RO B L E MS ?
  • 2. 2 S tories……
  • 3. S to ryN O .1
  • 4. Releas New Releasee Feature ??
  • 5. S to ryN O .2
  • 6. svn repositorylibs
  • 7. The only measure of progress is workingcode in source control.
  • 8. If it’s not in source control, it doesn’t exist...
  • 9. Get up-to-date before working on a file.
  • 10. Do not commit if code doesn’t pass localtesting or won’t even compile.
  • 11. Immediately commit after completing apiece of functionality.
  • 12. Every committed revision gives you arollback position.
  • 13. The risk of a merge nightmare increasesdramatically with time.
  • 14. It forces you to isolate features intodiscrete units of work.
  • 15. One commit for one purpose.One purpose into one commit.
  • 16. Do not commit any artifacts auto-generated out of the building process(e.g.program binary).
  • 17. Make sure all commit contain comments.
  • 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. 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