octave-maintainers
[Top][All Lists]
Advanced

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

Re: release 3.4.2


From: John W. Eaton
Subject: Re: release 3.4.2
Date: Sun, 19 Jun 2011 14:19:04 -0400

On 19-Jun-2011, Rik wrote:

| On 06/19/2011 10:00 AM, address@hidden wrote:
| > I think we should probably make a 3.4.2 release relatively soon.
| > 
| > jwe
| 
| Besides fixing the mkoctfile thing we might want to wait and see if this
| problem (https://savannah.gnu.org/bugs/?33564) also needs a resolution
| before a quick point release.

This one too: https://savannah.gnu.org/bugs/?33590

| And the larger question is whether we should have Release Candidates before
| releases?  A methodology with RC might, only might, have prevented the
| problem.  I only have access to a Linux machine and I build and test the
| distribution before release, but that misses the Mac OS X and Windows
| crowds completely.

Yeah, I probably should have done that.  What should we set the
version number to for release candidates of point releases?  Does
something like 3.4.1-rc1 cause trouble?  Are there any functions in
Octave or Octave forge that rely on compare_versions (for example)?
If so, I think that function fails if given something like
"3.4.1-rc1".  OTOH, it probably fails for things like "3.5.0+" as
well, and I don't remember complaints about that, so maybe this is a
non-issue.

jwe


reply via email to

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