octave-maintainers
[Top][All Lists]
Advanced

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

Re: Schedule for 3.4.1


From: Rik
Subject: Re: Schedule for 3.4.1
Date: Thu, 12 May 2011 11:07:08 -0700

On 05/12/2011 10:00 AM, address@hidden wrote:
> On 11-May-2011, Jordi GutiƩrrez Hermoso wrote:
> 
> | Should we start thinking about a 3.4.1 release? Perhaps release in a
> | month or so?
> 
> Or even sooner than that?  I don't think there should be much holding
> us up.  I know some people would like to see certain bugs fixed, but
> the current stable sources are in better shape than the 3.4.0 release,
> aren't they?  So is there any real reason to delay?  We can't
> guarantee that each point release will fix all bugs reported, and
> 3.4.2 can fix additional problems.  However, if it is possible, it
> would be nice to fix any serious regressions, provided that the fixes
> are not too risky.
> 
> jwe

5/12/11

I think we could do a point release at any time.  The new stable/default
methodology should make this easier.  However, isn't binary compatibility
broken between 3.4.0 and 3.4.1?  If memory serves, jwe discovered something
in the way configure.ac was set up that was embedding library versions.  It
is now fixed so that 3.4.1 will be compatible with 3.4.2, but we should
make a prominent note about it.  Also, PCRE was not required for the 3.4.0
branch, but *is* a requirement for 3.4.1 because of the way merges were
done and the abandonment of the 3-4-x branch.  Again, a prominent note
would help about the new requirements.

The only issue report I would like to see resolved is one with
configuration and where to place library files
(https://savannah.gnu.org/bugs/?32840).  Currently we are putting certain
libraries in libexcdir rather than libdir which is contrary to the GNU
coding standard
(http://www.gnu.org/software/autoconf/manual/autoconf.html#Installation-Directory-Variables).
 I know jwe had some concerns about parts of the patch supplied in the bug
report, so I would urge just doing the minimal change and putting the
libraries in libdir and not doing the rest of the naming changes.

--Rik


reply via email to

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