octave-maintainers
[Top][All Lists]
Advanced

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

Re: New release of control pkg.


From: Olaf Till
Subject: Re: New release of control pkg.
Date: Fri, 16 Feb 2018 22:47:27 +0100
User-agent: NeoMutt/20170113 (1.7.2)

On Fri, Feb 16, 2018 at 09:08:32AM -0500, Doug Stewart wrote:
> I want to make a new release of the control package, and it should be soon,
> so that the new version will get packaged with the next release of stable,
> and then the soon to come octave-4.4.0 .
> 
> I ave made a local release to myself for testing and found that it installs
> with default  and stable.
> 
> 
> What I am not clear about is how to get the new version on -forge web page.
> 
> Olaf, could you explain that part please?
> 
> There are lots of warning as the control pkg. is being installed, and I
> hope to work on these soon. so I see an immediate release of control-3.1.0,
> so that It can be tested before the next octave release for windows etc.
> Then some minor releases as I fix all the warnings and add more features.

I've noted you and Alexander now as the maintainers in the DESCRIPTION
file. Since Alexander has made some additions and fixes recently, we
should wait until he agrees that a new release should be made.

As for the release procedure, this is described at our web-page
(currently dead...). In essence, the package and html tarballs should
be put to the release tracker, noting their md5sums. But note that we
(Oliver or me) recreate the release anyway, so posting the tarballs is
only for double-checking that we release what you intended to be
released. You can leave out the double-check, then it's sufficient to
tell us the changeset id from which the release should be made. Also
note that you should _not_ tag the release changeset, this is done by
the admins.


The rest of this post only refers to the compiler warnings.

Currently, DESCRIPTION says

Depends: octave (>= 3.8.0).

This could probably be changed (?), but IMHO we should at least
support Octave versions as far back as 4.0.0, so this should also be
tested (could be done by an admin).

The warnings for deprecated ::nelem () can probably be simply fixed by
changing to ::numel (), since even Octave 4.0.0 already has ::numel().

The other warnings (with Octave 4.3+) need more work. I could do that
for you, if necessary. Or we could leave the warnings in, or silence
them with a compiler option in src/Makefile. But note that this just
postpones the work until Octave versions higher than 4.4, which
probably won't have the now deprecated symbols anymore, while 4.2
hasn't the respective new symbols.

Olaf

-- 
public key id EAFE0591, e.g. on x-hkp://pool.sks-keyservers.net

Attachment: signature.asc
Description: PGP signature


reply via email to

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