git - Strategy for extracting messages of most useful commits to changelog -

For this question

• There is a change for managers / customers:
• "Provide additional addresses to users"
• Not included "Bug Fixed where addresses were overwritten due to X"

<

Avoid to view ) to find the most important commitments for each build (most often inconsistent behind )

Today, we use Generally, strong> easy to read as a normal game changelog ("Fixed Balance Problems: X" and "Graphics Driver Y has given the game slowly") Comment Add flags such as

to message Referee | Rim: Fix:

In this way, my first rip is to add another flag to that flag, for example

Send the message for CL-Add: feature X (CL = changelog) and then pars all ^ CL- (| ref | rim | fix) to add to the changelog for.

But then, how will you contact about the possibility of making messages written for Changelogs (i.e.? Very high level); Or maybe many messages related to the same changelog problem, when the facility-branches are merged, should change message be removed? What are the features of SCM: S (for example GIT) that handle this issue for you?

In just words: Is there an industry standard strategy or tool to remove useful comment messages in changelogs sluggish?

I have tried this in the past with very little luck. In fact, it really seems to every developer to do more work, for every commitment, whether messaging their message is very scary for customers or developers generally make that decision Is not the right person, and at one time it is a little incompetent.

After a lot of experimentation, what has worked for me is trivial: just before every release, a person goes through the GIT logs since the last release and all the interesting things are a changelog file Writes in It really does not work much in other ways; Most work is fixed, phrasing is not needed and a special mindset is needed for the decision process, so it would be more efficient for a person to make a small one smaller than a group of developers at one time in a big batch. is. (Think of it this way: You do not have to swap the "committed message customer check" part of the cash and outside job.)

If you really want to tag this message, like the information, You should consider doing this with git notes instead of the least message. Then if it is screwed by incorrectly marking a person as wrong / bug / feature / etc. , You can update it by annotating it can fix.