On 02/28/13 15:24, Albrecht Schlosser wrote:
> We'll need to take care of this for the next release. Unfortunately there
> are several places with version numbers that need to be adjusted manually
> for each release. :-(
We probably should have a checklist as part of the CMP, or similar
document to describe the release process, so that we don't miss anything
obvious.
We can probably also automate the release number process, or at very
least centralize things so that all version #s come from one location.
I've had to do this with my own software, and found over the years I
use two approaches:
1) For large commercial software, I have a VERSION file in the
main directory with a single line in it: VERSION=#.#
This can be include'ed from Makefiles to define macros used
on everything from compile lines to Makefile construction
to documentation builds and tar filenames.
2) For small open source projects, my small 'release' script
usually grabs the first version number it finds in the CHANGES
log. This ensures I keep CHANGES up to date, and the version
number
doesn't have to be separately named. Makefiles get this number
by
running a small script to get the version# from CHANGES and
turns it
into a macro value.
The release script makes sure this value gets hardwired into files
that need it hardwired for release.
_______________________________________________
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs
