Developer Meetings/20120904

Attendees:

To discuss

• Feature Freeze and outstanding bugs
  • http://na-mic.org/Bug/roadmap_page.php
  • 1180: Slicer might load the wrong Python and other dlls.
• Testing of tutorial functionality
  • NA-MIC @ RSNA
  • Tutorial and Demo Planning
  • What can we automate?
  • What will be done manually and by whom?
• iGyne extension
• ITK4 dashboards setup: help is needed with the following machines:
  • http://slicer.cdash.org/buildSummary.php?buildid=38107
    • Remove line 59
    • Comment line 109 and set(CTEST_GIT_COMMAND "C:/Program Files (x86)/Git/bin/git.exe"). Full path is required !
  • http://slicer.cdash.org/buildSummary.php?buildid=38108
    • I would suggest not to build extension for the moment. set(WITH_EXTENSIONS FALSE)
    • I think packaging of Slicer ITKv4 should be done after the following issue is addressed: 2115. Indeed, we need a mechanism to distinguish packages that will be uploaded on Midas.
    • Note also that be enabling WITH_EXTENSIONS, it means that:
      • No extensions will be built with there is an error while building Slicer.
      • It applies only to the "testing" extensions available in Slicer/Extensions folder.
    • Extensions should be built instead using SlicerExtensionsDashboardScript.TEMPLATE.cmake
• CTK patch for review and integration
  • Could a CTK developer please review this pull request: https://github.com/commontk/CTK/pull/230 ?
    • Done! Thanks, Jc!
  • Helps address: http://na-mic.org/Mantis/view.php?id=2460
    • Now closed.

Conclusion

• Reviewed list of outstanding bug
  • Nicole and Steve discussed sceneview related issues
  • Issue 1180 has been targeted for 4.3 since it doesn't impact the user

• Discuss how tutorials will be tested
  • Agree on dividing the list of tutorials and having a developer being the "owner" and responsible for coordinating the testing of it
  • Tutorials should be updated for Slicer4

• Review how Andriy could fix its ITKv4 dashboard scripts

• After iGyne maintainer will have fix the corresponding description file and done some basic testing, extension will be integrated. See here