Re: Release 3.4.1

[Rik]

On 04/04/2011 07:14 AM, John W. Eaton wrote:
> Are there changes that break binary compatibility or any otherwise
> risky changes that have been applied to the default branch since the
> 3.4.0 release?
Is there a simple way to let Octave answer this question rather than having
to review all the changesets?

I'm only guessing at a process, but it would be something like this:
1) compile and install version 3.4.1
2) run octave-3.4.0
3) switch all library references over to the 3.4.1 libraries using path,
EXEC_PATH, and any other internal variables necessary.
4) run the full test suite and see if it passes.

--Rik