Oh, let me add that git notes may also be a good idea. Since changing or adding a note do not change the SHA1 of the commit, adding them a posteriori or editing them would work well.
Other pros I see are that you get visibility of what's remarkable in git log itself, and that's scriptable if we want to build conventional files for release notes. With notes, I think changelog entry by release branch happens out of the box, including cherry-picks, reverts, etc. My only concern is that the ProGit book mentions a few gotchas related to pushing and merges. Has that improved in the last versions of Git? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
