[Pkg-octave-devel] [soren at hauberg.org: [OctDev] Octave-Forge R2008-08-24]
Thomas Weber
thomas.weber.mail at gmail.com
Mon Aug 25 08:32:23 UTC 2008
Am Montag, den 25.08.2008, 10:10 +0200 schrieb Rafael Laboissiere:
> You have probably seen this:
>
> ----- Forwarded message from Søren Hauberg <soren at hauberg.org> -----
>
> From: Søren Hauberg <soren at hauberg.org>
> Subject: [OctDev] Octave-Forge R2008-08-24
> Date: Sun, 24 Aug 2008 22:01:32 +0200
> To: octave-dev at lists.sourceforge.net, help <help at octave.org>
> Message-Id: <1219608092.5898.9.camel at sh-laptop>
>
> Hi Everybody,
> I've just updated the packages at Octave-Forge
> (http://octave.sf.net/). A lot of bugs has been fixed, new features and
> functions have been implemented, and new packages have been added. The
> packages have been tested against Octave 3.0.2.
>
> Hope you enjoy the packages. If you have any problems, please report
> them to the octave-dev at lists.sourceforge.net mailing list.
>
> Søren
>
> ----- End forwarded message -----
>
> The effect is that every package from Octave-Forge had a bump in its version
> number, even though I doubt that there has been changes in the code of all
> packages.
Actually, I consider it unfortunate that individual maintainers can't
release their packages themselves. This would spread the load[1] and
non-active packages wouldn't cause work.
> This is a bit unfortunate for the DOG, but that's life, we should
> start to update the Debian packages. BTW, the first thing to do is to bump
> "OCTVER = 3.0.2" in debian/rules of octave-pkg-dev.
Do you want to upload to experimental? Unstable doesn't have 3.0.2 yet.
[1] It might even mean that octave-forge wouldn't need a release manager
at all. I mean, nobody loves infrastructure work.
Thomas
More information about the Pkg-octave-devel
mailing list