Revision as of 17:27, 9 January 2009

Home < Slicer3:Events

Slicer3 Events

the first product release of Slicer3 is scheduled for the AHM in January of 2008
there will be a code freeze on Nov. 15 2007
- if you want your module to be part of Slicer3.0 submit it by then
- After that date, we will only accept bug fixes. It means that there will be no features added after the freeze in the main trunk.
- Anyone working on new features can do so in their own branch and they will be responsible for merging these back into the trunk after the freeze is lifted (at which point the release will be in a maintenance branch).

Initial releases began end of March 2007
- Base code functional and usable
- Several usable modules include (auto segmentaiton, editor, registration...)
- Image Guided Therapy example modules
Updated versions summer 2007
- With DTI and other application modules
- Bug fixes and performance enhancements

The first set of user tutorials will be released in Fall 2007. Slicer3 programming courses will be released in January 2008.

Initial Testing with Core 3 participation
Base functionality in place, but still subject to API changes and other improvements.
Packaged versions not yet available, but testers are able to easily build their own versions.

@@ Line 3: / Line 3: @@
 == Upcoming ==
+=== Slicer3.4 ===
+* the first product release of Slicer3 is scheduled for Feb/March
+* there will be a code freeze on Jan 25 2009
+* Requirements:
+** The module is feature complete for the tasks advertised
+** The module has a test. See [http://wiki.na-mic.org/Wiki/index.php/Slicer3:Execution_Model_Testing here] for more information.
+** Module has documentation on the [[Documentation#Modules|Slicer wiki]] and a pointer to it in the Help tab.
+** After that date, we will only accept bug fixes. It means that there will be no features added after the freeze in the main trunk.
+** Anyone working on new features can do so in their own branch and they will be responsible for merging these back into the trunk after the freeze is lifted (at which point the release will be in a maintenance branch).
 === Slicer3.0 ===
@@ Line 10: / Line 21: @@
 ** if you want your module to be part of Slicer3.0 submit it by then
 ** After that date, we will only accept bug fixes. It means that there will be no features added after the freeze in the main trunk.
 ** Anyone working on new features can do so in their own branch and they will be responsible for merging these back into the trunk after the freeze is lifted (at which point the release will be in a maintenance branch).
 == Retrospective ==