View source for Slicer4.2Planning

[[Image:SlicerRt0.3_Screenshot_DVH_HeadNeck.png|thumb|right|320px]]
[[Image:AHM2012-JC.jpg|thumb|right|320px]]
Attendees: JC, Steve, Chris, Slicer Users, Slicer Developers, NA-MIC Engineers, and More!

Venue: Google hangout.

Hours: August 20th, 10am until ???

<b>To participate</b>, send your google+ account address to "Jean-Christophe Fillion-Robin" <JChris.FillionR@kitware.com> and he will invite you to the hangout.  The invites and a link to the google hangout will be sent to various email lists 5 minutes before the hangout starts on August 20th.

<b>The goal</b> of this meeting is to review outstanding bugs, find volunteers to fix them, and define the features needed in future releases of Slicer!

<b>This meeting is open to the community!</b> All are welcome and encouraged to participate.   Join us, contribute to Slicer, and participate in the meeting to make Slicer an even greater success!

Agenda:
http://na-mic.org/Mantis/roadmap_page.php

See also:
http://na-mic.org/Mantis/changelog_page.php

== Planning Considerations ==
* Goal is to have a robust set of features in a stable release to support dissemination efforts
** Prime target for 4.2 release is [http://www.rsna.org/Annual_Meeting.aspx RSNA Nov 25-30, 2012]
** Release must be available on Monday November 5, 2012 (3 weeks in advance) to support preparation of training materials and installation at RSNA. 
The [http://www.na-mic.org/Wiki/index.php/RSNA_2012 courses we teach at RSNA] are hands-on sessions in classrooms equipped with Windows computers. The computers are provided by a company that pre-load all of the different software platforms used to teach at RSNA. The software installation is done by the company three weeks before the meeting. The RSNA release must be ready and all tutorials must be tested by that date. No dead-line extension is possible.
*[http://www.na-mic.org/Wiki/index.php/RSNA2012_Planning RNSA 2012 Planning Table]
* Developers need to make realistic estimates of time required and time available to address targeted issues.  These estimates need to be taken into account when determining priorities.  Your colleagues will be depending on you to make realistic estimates so that they can plan accordingly.

== Schedule ==
<em> JC, Nicole, Andras, Steve, JC, J2, Andrey, Chris, Greg, and Stephen</em>
* Nov 1 have executable ready for RSNA
* Oct 15 to Nov 1 fix errors found by tutorial testing
* Oct 1 to Oct 15 formal tutorial testing organized by Sonia
* Sept 1 to Oct 1 bug fixes driven by tutorial testing conducted by developers
* Sept 1: Feature freeze for 4.2.

== Tasks ==
<em>JC, Nicole, Andras, Steve, JC, J2, Andrey, Chris, Greg, and Stephen</em>
* Extensions are our #1 priority: Macs, dependencies, etc.  These will be fixed for 4.2.
* ITKv4 is our #2 priority, but it isn't going to make it by Sept 1. Packaging and building generally works on all platforms according to Steve P, HOWEVER, it is extremely slow to load images and certain key modules still depend on ITKv3.   Please check with Steve for details.  Our fear is that this conversion is going to require extensive testing, and we don't have time for it.   So, we have decided that ITKv4 won't be in 4.2.
* Annotation system will be addressed by bug fixes to the current implementation.
* Data Bundle will be in by Sept 1.
* SceneViews will be addressed by bug fixes.
* System-level python will not be in 4.2 - we will continue with the current implementation.

== To Do's ==
* Week of Aug 20
** JC is going to re-assign bugs and features to different releases in more details this week.   We will all review and then move forward to getting it done.