In addition to all the great advice already provided...
I think the shared theme in all your questions is that they are stories about you instead of stories about programming.
All your questions begin with something like
I've been doing such and such and.....
Instead your questions should begin with something like,
What is a method of doing....
You should try and think of the heart of your question, and present only that, preferably with a quick example. The questions are tailored very much to your projects, instead they should be tailored to the generalizations of the problems you encounter in your projects.
I've been using Git for a while now, and I recently started using it to tag my releases so that I could more easily keep track of changes and be able to see which version each of our clients are running (unfortunately the code currently mandates that each client have their own copy of the PHP site; I'm changing this, but it's slow-going).
In any case, we're starting to build some momentum, I thought it would be really good to be able to show people what has changed since the last release. Problem is, I haven't been maintaining a changelog because I don't have a good idea of how to go about it. For this particular time, I can run through the log and manually create one, but that will get tiring very quickly.
I tried googling "git changelog" and "git manage changelog" but I didn't find anything that really talked about the workflow of code changes and how that coincides with the changelog. We're currently following Rein Henrichs' development workflow and I would love something that went along with that.
Is there a standard approach that I am missing, or is this an area where everybody does their own thing?
Thanks very much for your comments/answers!
Could become something like:
I use Git to manage an app. How could I show the changes made to my app from release to release? I'd like to present these changes in a well formatted manner that is easily understandable to non programmer users of the app.
I tag each release.
So far I've been manually going through the change log and summarizing it for each release. Is there a better way of doing this?
We are currently following Rein Henrichs' development workflow and I would love something that went along with that, but any help is appreciated!
That's a first draft, but the idea is to make the question useful to as many people as possible while maintaining its pertinence to your situation.