Re: [Liborigin-devel] [PATCH 2/5] Update LIBORIGIN_VERSION

[Knut F. <Knu...@gm...>]

[2010-11-05 00:09] Miquel Garriga <gbm...@gm...>:
> -/* version 0.0 2007-09-26 */
> -#define LIBORIGIN_VERSION 0x00070926
> -#define LIBORIGIN_VERSION_STRING "2007-09-26"
> +/* version 0.0 2010-10-29 */
> +#define LIBORIGIN_VERSION 0x00101029
> +#define LIBORIGIN_VERSION_STRING "2010-10-29"

Oops, should have been in the last release. I think you sent this update 
before, but I managed to miss this one. Ideally though, it should be updated 
shortly before release so as to match the version number of the tarball.

Which raises the question: How do we coordinate version bumps and releases? 
Can/should the current time stamp be inserted semi-automatically ("make 
release"), or should this be done manually shortly before release? I've made 
some good experiences with "git describe --tags --dirty --always" (plus a 
little magic to make it work also for release tarballs); however, this still 
requires "git tag `date --iso`" to be done before release, unless you want to 
change the versioning scheme.

Knut