We're going to start using a convention I've been using in perforce and on my
jobs for years now. Commit messages will have lines prefixed to convey what
type of change they are:
! major change / enhancement
+ minor change / enhancement
- bug fix
not worth mentioning in the release
No wrapping lines in your commit message. If you have 2 changes they go on
separate lines.
Couple examples:
+ Added the thingy to the stuff.
fixed some rdoc
or:
! Changed the file format for X. Not backwards compatible.
+ Added X v1 to X v2 translator.
- Fixed
This will help us prep releases even faster and make it easier to see at a
glance what changes require more review.
My "original" writeup (written for work) is here:
http://www.zenspider.com/~ryan/OnePagers/02_AutomatedChangelogs.pdf
_______________________________________________
Rubygems-developers mailing list
http://rubyforge.org/projects/rubygems
Rubygems-developers@rubyforge.org
http://rubyforge.org/mailman/listinfo/rubygems-developers
