title: Best practices for version control comments
body: <p>There is a lot of conversation about commenting code, but how about commenting on check-ins?</p>
  
  <p>I found this blog post:
  <a href="http://redbitbluebit.com/subversion-check-in-comment-great-practices/" rel="nofollow noreferrer">http://redbitbluebit.com/subversion-check-in-comment-great-practices/</a></p>
  
  <p>As the guy who is putting together the release notes, I am looking for ways to make that job easier.</p>
  
  <p>Currently we defined our own scheme with <code>&lt;Begin_Doc&gt;...&lt;End_Doc&gt;</code> for anything that should be published to our software customers.  But even for the internal stuff, I'd like to know the "why" for every change.</p>