Difference between revisions of "2010 Slicer36 Module Cull"

From NAMIC Wiki
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
 
*This is a review session which is open to all Slicer developers and the project leadership.  
 
*This is a review session which is open to all Slicer developers and the project leadership.  
 +
*[http://slicer.spl.harvard.edu/slicerWiki/index.php/Slicer3:3.6Release see the 3.6 release schedule for reference]
 
*Call-in will be available
 
*Call-in will be available
 
*We will begin the session in 1249 Boylston St. at 11am EST on Thursday 4/29.
 
*We will begin the session in 1249 Boylston St. at 11am EST on Thursday 4/29.
Line 13: Line 14:
 
**the remainder up to the contributors, we will grade the extensions
 
**the remainder up to the contributors, we will grade the extensions
  
=Luis Ibanez' score system=
 
** Gold:  have > 80% coverage,      0 Valgrind errors, documentation and tutorial
 
** Silver: have > 70% coverage, <  10 Valgrind errors, documentation and tutorial
 
** Bronze: have > 60% coverage, <  50 Valgrind errors, documentation and tutorial
 
** Coal:  have < 10% coverage, > 1000 Valgrind errors, no documentation, no tutorial
 
 
=Repository of grading for 3.6 modules and extensions=
 
=Repository of grading for 3.6 modules and extensions=
 
See [http://wiki.slicer.org/slicerWiki/index.php/Slicer-3.6-QA here] for the 3.6 QA table.
 
See [http://wiki.slicer.org/slicerWiki/index.php/Slicer-3.6-QA here] for the 3.6 QA table.

Latest revision as of 02:30, 29 April 2010

Home < 2010 Slicer36 Module Cull
  • This is a review session which is open to all Slicer developers and the project leadership.
  • see the 3.6 release schedule for reference
  • Call-in will be available
  • We will begin the session in 1249 Boylston St. at 11am EST on Thursday 4/29.
  • We will review the documentation and status of module candidates for Slicer 3.6
  • Slicer 3.6 modules which are distributed as part of the Slicer download are expected to have the following:
    • In-module help and acknowledgment
    • Documentation on the Slicer wiki
    • Test coverage (as possible, we currently do not have automated testing for gui interactions)
    • Coverage in tutorials (where it makes sense)
  • Extensions for Slicer 3.6:
    • In-module help and acknowledgment are mandatory
    • documentation on the Slicer wiki (see above) is strongly suggested
    • the remainder up to the contributors, we will grade the extensions

Repository of grading for 3.6 modules and extensions

See here for the 3.6 QA table.