3

I'm looking for any books considered best practice, canon, etc. on source code management (SCM) practices for developers. Something that gives guidance on how and when to branch, how and when to merge, version number schemes, etc.

Perhaps with an eye towards distributed SCM tools like git (vs svn/cvs?), geographically distributed vs. centrally located development teams, differences between practices during forward development and post production, etc.

EJoshuaS - Stand with Ukraine
  • 11,977
  • 56
  • 49
  • 78
Michael Campbell
  • 2,022
  • 1
  • 17
  • 22
  • Any chance you can give more specific details about the process and tools you are interested in? Effective strategies for using SCM depend on both your development process and your SCM tools; "when should I branch?" probably has a very different answer if you are using SVN than if you are using git and "post production" means different things depending on if you are releasing binary packages or pushing continuous releases to a web service. – Jonah Jan 05 '11 at 18:09
  • Resource recommendation requests are off topic here. – EJoshuaS - Stand with Ukraine Jul 16 '17 at 05:28
  • > Resource recommendation requests are off topic here. – EJoshuaS ...he says, 5 1/2 years later. – Michael Campbell Jul 19 '17 at 16:34

2 Answers2

2

I am not sure there is one book, but at least you have:

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
2

Not paper books however you should check :

Community
  • 1
  • 1
OneOfOne
  • 95,033
  • 20
  • 184
  • 185