Re: Unmaintained packages - becoming a maintainer?

[Julien Bect]

Le 21/05/2015 07:15, address@hidden a écrit :

I've got as far as setting up a Jenkins build and writing a bit of blog
about it here: http://www.neilhopcroft.com ...which I hope shows at least
a little bit of interest in the project.

Hello Neil,

Very interesting.

Having regularly updated reports on the status of Octave packages would be great. Even better would be to have some code coverage statistics associated to the unit tests, but we're not there yet. In the same spirit, you should look at the recent effort by Oliver Heimlich:

http://wiki.octave.org/Octave-Forge#GNU_Octave_4.0_compatibility_assessment.

Now, as one of the maintainer of the stk package, I have some questions for you:

1) In your post "Octave Packages CI build dependencies", you report "Build error" for stk, but you don't provide the version of stk (nor the version of Octave) that you have tested. Could you please tell me more about this "Build error"? A release was made very recently (2.3.0), could you try it and see if the build error is still there?

2) In your post "Current state of unmaintained octave packages" you report stk as an unmaintained package, which it is not. What is the reason for this classification?

Please email this list as soon as you post new results on your blog, results of this kind are obviously of great interest for the OF community.

@++
Julien