Difference between revisions of "Developer Meetings/20120904"

From Slicer Wiki
Jump to: navigation, search
 
(9 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
* Feature Freeze and outstanding bugs
 
* Feature Freeze and outstanding bugs
 
** http://na-mic.org/Bug/roadmap_page.php
 
** http://na-mic.org/Bug/roadmap_page.php
 +
** [http://na-mic.org/Mantis/view.php?id=1180 1180]: Slicer might load the wrong Python and other dlls.
 
* Testing of tutorial functionality
 
* Testing of tutorial functionality
 
** [http://www.na-mic.org/Wiki/index.php/RSNA_2012 NA-MIC @ RSNA]
 
** [http://www.na-mic.org/Wiki/index.php/RSNA_2012 NA-MIC @ RSNA]
Line 9: Line 10:
 
** What can we automate?
 
** What can we automate?
 
** What will be done manually and by whom?
 
** What will be done manually and by whom?
 +
* [https://github.com/Slicer/ExtensionsIndex/issues/67 iGyne extension]
 
* ITK4 dashboards setup: help is needed with the following machines:
 
* ITK4 dashboards setup: help is needed with the following machines:
 
** http://slicer.cdash.org/buildSummary.php?buildid=38107
 
** http://slicer.cdash.org/buildSummary.php?buildid=38107
Line 15: Line 17:
 
** http://slicer.cdash.org/buildSummary.php?buildid=38108
 
** http://slicer.cdash.org/buildSummary.php?buildid=38108
 
*** I would suggest not to build extension for the moment. <code>set(WITH_EXTENSIONS FALSE)</code>
 
*** I would suggest not to build extension for the moment. <code>set(WITH_EXTENSIONS FALSE)</code>
*** I think packaging of Slicer ITKv4 should be done after the following issue is addressed: [http://na-mic.org/Mantis/view.php?id=2115 2115]. Indeed, we need a mechanism to distinguish package that will be uploaded on Midas.
+
*** I think packaging of Slicer ITKv4 should be done after the following issue is addressed: [http://na-mic.org/Mantis/view.php?id=2115 2115]. Indeed, we need a mechanism to distinguish packages that will be uploaded on Midas.
 +
*** Note also that be enabling <code>WITH_EXTENSIONS</code>, 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 <code>Slicer/Extensions</code> folder.
 +
*** Extensions should be built instead using [https://github.com/Slicer/Slicer/blob/master/Extensions/CMake/SlicerExtensionsDashboardScript.TEMPLATE.cmake SlicerExtensionsDashboardScript.TEMPLATE.cmake]
 
* CTK patch for review and integration
 
* CTK patch for review and integration
 
** Could a CTK developer please review this pull request: https://github.com/commontk/CTK/pull/230 ?
 
** Could a CTK developer please review this pull request: https://github.com/commontk/CTK/pull/230 ?
Line 23: Line 29:
  
 
== Conclusion ==
 
== Conclusion ==
 +
 +
* Introduced [http://www.kitware.com/company/team/jhaveri.html Sankhesh] (Kitware Inc) to the rest of the team. Sankhesh will also be helping us to improve Slicer.
 +
 +
* 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
 +
** Steve will be contacting each developer with a list of tutorials
 +
** 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 [https://github.com/Slicer/ExtensionsIndex/issues/67 here]

Latest revision as of 20:55, 4 September 2012

Home < Developer Meetings < 20120904

Attendees:

To discuss

Conclusion

  • Introduced Sankhesh (Kitware Inc) to the rest of the team. Sankhesh will also be helping us to improve Slicer.
  • 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
    • Steve will be contacting each developer with a list of tutorials
    • 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