[Plplot-devel] Re: Bumping the version numbers in configure.ac

[Thomas J. D. <to...@fi...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Alan,

     Yes, I agree with you, and will do this unless there are
objections.  I'm going to announce a "test release" shortly of my most
recent build, which will have the long name.  When everybody is happy that
the build is working properly, I will create the "official 5.5.0
development release" (no cvs.date stamp), and we will keep the shorter
numbers thereafter.  I will stay with the long numbers until then so that
the test builds don't get confused with the real development release.
The test builds will only be available from my Web site (i.e., not
posted on sourceforge).

Cheers,
Tom

- --

On Sat, 5 Mar 2005, Alan W. Irwin wrote:

> On 2005-03-05 17:11-0000 Thomas J. Duck wrote:
>
> > Update of /cvsroot/plplot/plplot
> >
> > -AC_INIT(plplot, 5.3.1.cvs.20040822, plp...@li...)
> > +AC_INIT(plplot, 5.5.0.cvs.20040822, plp...@li...)
> > AC_REVISION($Revision$)
> >
> > dnl Date of release.  This can be set by hand, but the prefered method
> > dnl is by specifying one of the option --version of --date-version to
> > dnl bootstrap.sh
> >
> > -RELEASE_DATE=2004-08-22
> > +RELEASE_DATE=2005-03-01
> > AC_SUBST(RELEASE_DATE)
>
> Hi Tom,
>
> I think we should discuss the way release numbers are bumped in configure.ac.
>
> Our tradition has been to use the old number (5.3.1 in this case) along with
> the .cvs.YYYYMMDD suffix to show this is a cvs snapshot after the release of
> 5.3.1.  So under that old scheme the release number for a cvs snapshot today
> would be 5.3.1.cvs.20050305 with corresponding release date of 2005-03-05.
> Both the YYYYMMDD suffix and release date would continue to be incremented
> for each cvs snapshot until we were ready for release of 5.3.2 (under the
> old versioning scheme).
>
> Of course, you are not making a cvs snapshot.  Instead, the plan is to
> release an experimental version every two weeks.  My view is that under this
> new scheme the method of bumping numbers in configure.ac doesn't have to be
> nearly as complicated as before. If you really are going to release every
> two weeks you could simply change the version number and release date just
> on the day of the release.  Of course, under this scheme there is no need
> for .cvs.YYYYMMDD suffixes so the version numbers in configure.ac for the
> next few experimental releases would simply be 5.5.0, 5.5.1, etc.
>
> I offer this suggestion of a simplified method of bumping the numbers in
> configure.ac simply to give you some food for thought and because I like the
> KISS principle.  However, your opinion as RM is the most important one here
> since you are the one that has to deal with the consequences of whatever
> number bumping scheme you ultimately decide to follow in configure.ac.
>
> 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 FreeEOS equation-of-state implementation
> for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
> package (plplot.org); the Yorick front-end to PLplot (yplot.sf.net); the
> Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project
> (lbproject.sf.net).
> __________________________
>
> Linux-powered Science
> __________________________
>

- --
Thomas J. Duck <to...@fi...>

  Department of Physics and Atmospheric Science, Dalhousie University,
    Halifax, Nova Scotia, Canada, B3H 3J5.
  Tel: (902)494-1456 | Fax: (902)494-5191 | Lab: (902)494-3813
  Web: http://aolab.phys.dal.ca/~tomduck/
  Public key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x17D965DB
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCKfrrndxDHhfZZdsRAqq3AJ9x448ECjZ0yk0A1DampJv9ZyETSQCfZUVn
dTxI2IMLTErw/XEjPQ3hNeg=
=vj6p
-----END PGP SIGNATURE-----