On 2006-04-02 23:05-0400 hbabcockos1@... wrote:
> On Mar 30, 2006, at 2:46 AM, Alan W. Irwin wrote:
>> we have released before). However, if you want to stick with the current
>> advertised convention, then calling the next (presumably stable) release
>> 5.6.0 is the correct thing to do.
> Ok. 5.6.0 it is.
>> If you could please save the output of cf/bootstrap.sh (which completely
>> describes the autotools versions used) in the release notes, then there
>> be no ambiguity about what autotools versions were used to create the
>> release tarball, and it should be straightforward for any developer to
>> replicate the release tarball from the cvs version of date.
> Sure. This reminds that there was some discussion about whether the release
> notes should just cover the current version, or whether they should also have
> the previous versions release notes appended. Was that resolved?
Yes. One section of README.release has changes relative to our last
developmental release, PLplot-5.5.3 while another has overall changes
relative to our last stable release, PLplot-5.3.1. I think if we do
development releases in the future, we should use that two-track system
again. However, for now since this release is stable, I think you can drop
the first section (which presumably only includes redundant information with
the second section) and simply state the overall changes since our last
stable release, PLplot-5.3.1.
>> Part of the release process is to generate a ChangeLog automatically from
>> the cvs commit messages. For example, I used to do this with the cvs2cl
>> "-d< today" --stdout > ChangeLog.test command, although there may be a
> Ok. Unfortunately developer CVS access at Sourceforge is currently down so I
> didn't make much headway this weekend beyond figuring out how to build the
I remember just how difficult it used to be to build the documentation so I
am pleased it is so much easier now.
From the sourceforge status page it looks like the cvs issue is due to
hardware troubles. Hopefully, they will get it straightened out in a hurry
since there an awful lot of projects (including PLplot) that depend on that
Alan W. Irwin
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