Re: [Plplot-devel] PLplot version string for the current CVS version

[Alan W. I. <ir...@be...>]

On Wed, 12 Mar 2003, Alan W. Irwin wrote:

> Rafael and I have been discussing this topic recently since it makes no
> sense to call our documentation version 5.2.0 when it is clearly done after
> that release.  Same goes for any tarball we create now leading up to our
> next release.  It makes no sense to call it 5.2.0, but it also makes no
> sense to call it say 5.2.1.pre since we are not actually sure of that number
> until actual release time when the version decision will be made.  We both
> agree that old version suffixed with cvs and date (e.g., 5.2.0.cvs.20030303)
> would work.

Actually, Rafael does not agree with this idea.  He has just reminded me
privately that if the version is changed on a daily basis then that means
recompiling *everything* every time you run bootstrap.sh which of course
would be unacceptable.  So I think the best compromise is to change our
current configure.ac so the version string is 5.2.0.cvs, and add an option
(mostly to be used for special circumstances such as making a pre-release
tarball to be publically made available to testers or building pre-release
documentation for our website) to bootstrap.sh to add the date to that
static version string.  Since this option won't affect most developers the
only question remaining for discussion here is whether there is any
objection to old.release.number.cvs (e.g., 5.2.0.cvs) as the static version
number between releases?

Alan

__________________________
Alan W. Irwin
email: ir...@be...
phone: 250-727-2902

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the Canadian Centre for Climate Modelling and
Analysis (www.cccma.bc.ec.gc.ca) and the PLplot scientific plotting software
package (plplot.org).

__________________________

Linux-powered Science
__________________________