[development] Reviewing patches and making decisions -> Sociocracy could be a way to go!

[Aaron Winborn]

What's the 'standard commit message pattern'? I thought I read once it 
was something like '#nid/username: comment', but can't find that 
anywhere. For readability, I just copy the comments from my changelogs, 
which usually follows something like 'Month, Year\n-----------\n * #nid: 
comment (username).' (Leaving out the M/Y obviously, since that's 
already present in the CVS logs). But I'd like to do this properly in 
the future.

Thanks,
Aaron

Angela Byron wrote:
>
> This is actually a feature built into CVS (and most other version 
> control systems) called CVS Annotate that does exactly that:
> http://www.lullabot.com/articles/cvs_annotate_or_what_the_heck_were_they_thinking 
>
>
> For every line of code, you can discover who made the change, when 
> they made it, and why. Assuming the maintainer is following standard 
> commit message patterns, you can also reference the original issue 
> that has all the background information on discussions on the code 
> that were had, the development evolution of the feature over time, and 
> why the decision was ultimately made to commit it.
>
> It's a pretty awesome resource because it's automatically updated with 
> every commit, without the need for any manual intervention or extra 
> overhead.
>
> -Angie
>


-- 
Aaron Winborn

Advomatic, LLC
http://advomatic.com/

Drupal Multimedia Available Now!
http://www.packtpub.com/create-multimedia-website-with-drupal/book

My blog:
http://aaronwinborn.com/