octave-maintainers
[Top][All Lists]
Advanced

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

Re: feature freeze -> 3.0 release


From: Shai Ayal
Subject: Re: feature freeze -> 3.0 release
Date: Sun, 23 Sep 2007 13:37:59 +0200

On 9/23/07, Thomas Weber <address@hidden> wrote:
> Am Samstag, den 22.09.2007, 09:57 +0100 schrieb Shai Ayal:
> > On 9/22/07, Søren Hauberg <address@hidden> wrote:
> > > David Bateman skrev:
> > > > The only thing I really really want to see fixed before 3.0 is that at
> > > > least one distribution is happy with the octave package manager. After
> > > > the changes to pkg.m are in can we have at least one test release prior
> > > > to a full release? In that case might we have a 2.9.15 is a very short
> > > > time if I get a patch together for pkg.m that Orion is happy with? If so
> > > > I'd put off an octave-forge release for 2.9.14 to get pkg right and
> > > > release octave-forge based on 2.9.15.
> > > I agree very much with these thoughts! I consider the package manager
> > > broken if no distributors picks it up...
> >
> > I agree -- this is the key issue which should be solved before 3.0 --
> > it is very telling that fedora core's last rpm is from 2.9.9 (I think)
>
> It just tells that Quention doesn't have much time (which I think he
> said on the list).
>
>
> > -- It would be a shame to release a major release which would not be
> > distributed in the major distributions.
>
> Most distributions have more or less up-to-date versions of Octave in
> their development branches.
>
I/m sorry, I work with fedora. So is the package problem solved for,
lets say, debian? If so than maybe this isn't really a problem and
3.0.0 shouldn't be delayed

Shai



reply via email to

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