Robert,
I made some changes to the share makefile in the release branch just
yesterday, because some files were not installed by make install. I also
noticed that there are several failures in share_testsuite and one failure
in the main testsuite with CMUCL 19c only:
Error found in tests/rtest4.mac, problem: (86) [CMUCL ONLY]
Error found in share/contrib/rtest_opproperties.mac, problem: (72)
Error found in share/contrib/stats/rtest_stats.mac, problem: (9) [CLISP
ONLY]
Error found in share/contrib/levin/rtest_levin.mac, problem: (62)
Other than this, everything seems to be working fine with
CMUCL/GCL/CLISP/SBCL on my Linux box.
Viktor
-----Original Message-----
From: maxima-bounces at math.utexas.edu [mailto:maxima-bounces at math.utexas.edu]
On Behalf Of Robert Dodier
Sent: Saturday, April 19, 2008 11:31 AM
To: Maxima List
Subject: Maxima 5.15.0 release plan
Hello,
The 5.15.0 release candidate 1 seems to work OK to judge by
the lack of complaints. A few minor changes have been
committed to the release branch. What I would like to do at this
point is to tag the existing stuff on the release branch
(rc1 + accumulated changes) and release it as 5.15.0.
If some more changes are required (in particular if there are
installation problems) then we can commit a fix to
the release branch and release 5.15.1.
I'd like to change the release process to do away with the
release candidates and just release x.y.0 as the first version
on a release branch, then x.y.1, x.y.2 etc as necessary.
The main difference wrt the current scheme is that the
current scheme requires a redundant re-release of the
final release candidate as the official x.y.0.
There's no need for that.
Also I think the x.y.0, x.y.1, etc scheme is slightly more rational.
Your friendly project administrator,
Robert Dodier
_______________________________________________
Maxima mailing list
Maxima at math.utexas.edu
http://www.math.utexas.edu/mailman/listinfo/maxima