Reviewing Octave Forge packages: Difference between revisions

→‎Checklist: add versions, permissions, and licence check info
(→‎Checklist: add versions, permissions, and licence check info)
Tags: Mobile edit Mobile web edit
Line 22: Line 22:
[ ] maintainer has specified a corresponding revision commit/changeset
[ ] maintainer has specified a corresponding revision commit/changeset
[ ] checkout code from Sourceforge, commit/changeset is present
[ ] checkout code from Sourceforge, commit/changeset is present
== Compile and Install ==
== Compile and Install ==
[ ] release candidate installs on latest stable Octave release
[ ] release candidate installs on latest stable Octave release
Line 31: Line 32:
[ ] no makeinfo errors and warnings during HTML build
[ ] no makeinfo errors and warnings during HTML build
[ ] unpacked and spot-checked the generated HTML documentation
[ ] unpacked and spot-checked the generated HTML documentation
== Interaction with pkg ==
== Interaction with pkg ==
[ ] <code>pkg load foo</code> runs with errors or warnings
[ ] <code>pkg load foo</code> runs with errors or warnings
Line 40: Line 42:
     *  ________
     *  ________


== Package files ==
== Package files in release candidate tarball ==
[ ] tested with minimum Octave version list in DESCRIPTION
[ ] tested with minimum Octave version list in DESCRIPTION
[ ] reasonable dependencies listed in DESCRIPTION
[ ] reasonable dependencies listed in DESCRIPTION
[ ] NEWS file makes sense, version and date match
[ ] NEWS file makes sense, version and date match
[ ] All functions are listed in INDEX
[ ] All functions are listed in INDEX
[ ] check licenses (<code>licensecheck -r</code> "plus some manual checks").
[ ] package files are readable/executable by all users (reasonably current maintainer Makefile should be doing this).
[ ] version number in src/configure.ac (if present) matches DESCRIPTION and tarball name.
[ ] any version numbers within the help or function body (e.g., banners) matches above.
</pre>
</pre>


110

edits