Preparing a new client release
Posted: Sun Nov 27, 2011 10:56 am
In the process of preparing a new client tarball release, so far I've compiled a `NEWS' file which contains the most important changes in the current client code base since the last release (1.4.0 from 2007-12-11). I looked up the changes from the `git whatchanged' output, which is like:
http://bloodspilot.git.sourceforge.net/ ... ents;a=log
, plus a list of the modified files for each change, so that I could easily see which clients where affected by each change.
I'll post the `NEWS' file for preview next time.
I am loosely following the recommendations of the GNU Coding Standards:
http://www.gnu.org/prep/standards/standards.html
(see chapters 6 and 7).
I find a `Changelog' file like:
http://bloodspilot.git.sourceforge.net/ ... 97;hb=HEAD
quite handy. It gives more detailed information than the `NEWS' file, including all changes, which files and ideally which functions where changed. Note that the file linked above is not optimal, partly due to my big patches, which do not include information about changed files and functions.
The question is how to create such a `Changelog' file from the GIT repository? `git log' and `git whatchanged' give useful results, but are different (e.g. no information about changed functions and different formatting).
Other missing parts are an introductory `README' file and updating `INSTALL' (perhaps integrating `INSTALL.ubuntu' into `INSTALL'). The question here is whether the mentioned dependencies are still up-to-date?. Is there some automatic way to find out about the dependencies?
Otherwise there remain some very minor code fixes (which I've mostly done in my local code base) and then we could finally release the new tarball.
http://bloodspilot.git.sourceforge.net/ ... ents;a=log
, plus a list of the modified files for each change, so that I could easily see which clients where affected by each change.
I'll post the `NEWS' file for preview next time.
I am loosely following the recommendations of the GNU Coding Standards:
http://www.gnu.org/prep/standards/standards.html
(see chapters 6 and 7).
I find a `Changelog' file like:
http://bloodspilot.git.sourceforge.net/ ... 97;hb=HEAD
quite handy. It gives more detailed information than the `NEWS' file, including all changes, which files and ideally which functions where changed. Note that the file linked above is not optimal, partly due to my big patches, which do not include information about changed files and functions.
The question is how to create such a `Changelog' file from the GIT repository? `git log' and `git whatchanged' give useful results, but are different (e.g. no information about changed functions and different formatting).
Other missing parts are an introductory `README' file and updating `INSTALL' (perhaps integrating `INSTALL.ubuntu' into `INSTALL'). The question here is whether the mentioned dependencies are still up-to-date?. Is there some automatic way to find out about the dependencies?
Otherwise there remain some very minor code fixes (which I've mostly done in my local code base) and then we could finally release the new tarball.