On Thu, Mar 14, 2019 at 16:16:00 +0100, JuanPi wrote:
> So how we speed up and make easier the release process?
I don't know if it's documented anywhere, but I would review by
1. Pick a package at https://sourceforge.net/p/octave/package-releases/
2. Install the release candidate in latest Octave release
3. Look for compiler errors and warnings
4. Run all tests using runtests (including tests in the src dir)
5. Run doctest on all functions (optional)
6. Repeat steps 2-5 in other versions of Octave as available
7. Run generate_package_html
8. Look for makeinfo errors and warnings during HTML build
9. Unpack and spot-check the generated HTML documentation
10. Read NEWS and see if it makes sense, version and date match
11. See if all functions are listed in INDEX
I think what JuanPi is referring to is the step 12: Some Octave Forge admin has to accept the reviewed package put the released tarball to [1], and finally announce the package update on the website (updated list of functions and so on) to make `pkg install -forge` work.
Oliver did lots of work last year to make Octave Forge a great website and to formulate a SourceForge based release procedure. I am too little involved in this project to judge the real effort, but I have the impression, that things are too complicated this year for the current manpower. Is Oliver currently the only one who can do this final package release steps? The SourceForge release list [2] counts 13 pending items over two months. Did the Octave Forge release process stall?
Kai