octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: release 3.2.1


From: Jaroslav Hajek
Subject: Re: release 3.2.1
Date: Fri, 3 Jul 2009 18:55:38 +0200

On Fri, Jul 3, 2009 at 2:16 PM, Jaroslav Hajek<address@hidden> wrote:
> hello,
>
> The Octave 3.2.1 semi-official tarballs are available at
> http://artax.karlin.mff.cuni.cz/~hajej2am/ulozna/octave/
>
> We have 82 patches (mostly bug and doc fixes) since the 3.2.0 release.
> I sincerely thank all contributors and testers for their valuable
> work.
> If your favorite bug was not fixed, don't give up hope; Octave is going on :)
>
> John, please upload the tarballs to the GNU FTP site.
>
> free computing, free society!
>

OK, so hold up the fanfares; the release is flawed and should not be
used. I've removed the tarballs. See this thread:
http://www.nabble.com/Bug-in-octave-3.2.x-with-custom-atlas-multithread-td24319610.html
In short, any use of unwind_protect can cause a segfault (depending on
calling sequences).

The development version does not suffer from this problem; it's caused
by a special patch created (by me) for 3.2.x rather than transplanting
from the development version to avoid breaking ABI compatibility.

This is similar to the issue of 3.0.4 - a very serious bug was
reported very shortly after the release. Also, the bug was caused by a
patch specialized for the stable branch to avoid breaking the ABI.

Since this is the second time I've managed to produce a flawed
release, I think I'm doing a poor job as the stable branch manager,
and it's time for a change. Who wants to take on the role?

Forgive me my bitterness, but I'm really disappointed.

Sorry for all the noise. Please don't use the tarballs (if you already
downloaded them) for packages. Recent RCs also suffer from the bug;
right now I can't check which ones.

best regards

-- 
RNDr. Jaroslav Hajek
computing expert & GNU Octave developer
Aeronautical Research and Test Institute (VZLU)
Prague, Czech Republic
url: www.highegg.matfyz.cz


reply via email to

[Prev in Thread] Current Thread [Next in Thread]