Agenda&Status 041307: Difference between revisions
From KitwarePublic
Jump to navigationJump to search
(New page: == Agenda == === Project Management === * Schedule ** Next release 3.4 http://www.itk.org/Wiki/ITK_Release_Schedule#Release_3.4_Schedule ** Feature freeze June...) |
No edit summary |
||
| Line 26: | Line 26: | ||
** Subsamples | ** Subsamples | ||
** Iterators [[Proposals:Refactoring Statistics Framework 2007 Iterators | Iterators Review ]] | ** Iterators [[Proposals:Refactoring Statistics Framework 2007 Iterators | Iterators Review ]] | ||
** Status: | ** Status: [[Proposals:Refactoring Statistics Framework 2007 Action Items | Action Items ]] | ||
** DEPRECATION STRATEGY | |||
*** Keep old classes around for 2 or 3 releases | |||
*** Add CMake option to select at configuration time between the old Statistics and the new ones | |||
*** Provide a migration guide: for all old classes, describe which new classes are replacing them. | |||
Latest revision as of 16:27, 13 April 2007
Agenda
Project Management
- Schedule
- Next release 3.4 http://www.itk.org/Wiki/ITK_Release_Schedule#Release_3.4_Schedule
- Feature freeze June 1st 2007
- Release June 30th 2007
Technical Topics
- MersenneTwister Random number generator Singleton versus MultiThreaded issues.
- Crashes when called from multiple threads because it modify static variables
- It was converted to singleton in order to make testing deterministic. (seed initialization)
- Are mutex locks prohibitive ?
- How to fix it and still keep Backward Compatibility ?
- ResampleImageFilter new ReferenceImage had no test.
- How to prevent developers from adding new features without a test ?
- ResampleImageFilter was using an extra member variable and using a second input.
- VectorResample filter API
- adjusting API to fit the ResampleImageFilter (TODO)
- Statistics classes refactoring (to be included in ITK 3.4)
- Refactoring Statistics Framework 2007
- Analysis of class structures
- Subsamples
- Iterators Iterators Review
- Status: Action Items
- DEPRECATION STRATEGY
- Keep old classes around for 2 or 3 releases
- Add CMake option to select at configuration time between the old Statistics and the new ones
- Provide a migration guide: for all old classes, describe which new classes are replacing them.
