Reviewing Octave Forge packages: Difference between revisions

Reviewing Octave Forge packages (edit)

Revision as of 02:55, 1 October 2020

826 bytes removed , 1 October 2020

Overhaul page.

Siko1056

Bureaucrats, Administrators

1,847

edits

@@ Line 1: / Line 1: @@
-== Help reviewing Octave Forge packages ==
+{{Note|More than one person can review a package, in fact that would be great.}}
-We need help. Here is how:
+The reviewing procedure in short:
 # Pick a package at https://sourceforge.net/p/octave/package-releases/
@@ Line 10: / Line 10: @@
 #* <code>[F]</code> for fails.
 # Paste your filled in check-list as a comment on the issue above
+# An [https://sourceforge.net/p/octave/_members/ Octave Forge Admin] will try to look over your review and hopefully release the package.
-=== What happens next ===
-An admin will try to look over your review and hopefully release the package.  More than one person can review a package, in fact that would be great.
 == Checklist ==
@@ Line 53: / Line 49: @@
 [ ] contains no hidden dot files, junk backup files, results of configure runs, etc (should be taken care of by maintainer Makefile).
 </pre>
-== Other info ==
-TODO:  how does one check all functions are listed in INDEX?
-: Carne Draug wrote a script to do this several years ago. It is in the [https://sourceforge.net/p/octave/code/HEAD/tree/trunk/octave-forge/admin/check_INDEX.pl old OF admin repository] [[User:KaKiLa|KaKiLa]] ([[User talk:KaKiLa|talk]]) 07:56, 20 November 2019 (PST)
-TODO: document how to run "all tests including those in src"  Someday this should be just "pkg test foo".
-TODO: would be good to provide more specific instructions for when the package as a Maintainer Makefile?  But we don't usually put the Maintainer Makefile in the .tar.gz package to do?  (At least Doctest and Symbolic don't).
-=== Meta helping ===
-* Feel free to edit this wiki with explanations of the check list tasks
-* Please do add (reasonable) tasks to the check list
 === Common problems ===