|
From: | Orion Poplawski |
Subject: | Re: Release 3.4.1 |
Date: | Mon, 04 Apr 2011 15:54:34 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b3pre Thunderbird/3.1.9 |
On 04/04/2011 02:50 PM, Rik wrote:
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
You could submit octave to: http://linuxtesting.org/upstream-tracker/I've found that quite helpful. Be sure to point them to the development source as well.
-- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA/CoRA Division FAX: 303-415-9702 3380 Mitchell Lane address@hidden Boulder, CO 80301 http://www.cora.nwra.com
[Prev in Thread] | Current Thread | [Next in Thread] |