Hello, We have entered the Release Candidate cycle for ITK 4.2.
This means that we are entering a feature freeze for the ITK repository until ITK 4.2 is tagged at the end of June. So there should be no topics which are enhancements, new features or for performance ( ENH, or PERF ) merged. The goal of this is to all time for developers to clean up errors on the dashboard, improve coverage, and documentation. Along with when the release candidates are made allow time for users to test the potential new release to ensure that there are no regressions, or unnoticed critical bugs. Additionally, there needs to be time for WrapITK and SimpleITK to polish up their wrapping while the code is not changing. For example it would be great if some of these failing tests could be addressed: http://open.cdash.org/viewTest.php?onlyfailed&buildid=2317940 http://open.cdash.org/testDetails.php?test=147964451&build=2319926 http://open.cdash.org/testDetails.php?test=147964451&build=2319926 Additionally, I would like to pose the challenge to the ITK community to raise the level of converge 1% from 83.49 to 84.5% which would require ~1200 more line of code to be tested. Currently the committers to the repository are not restricted. We hope that are developers will be responsible and addible by the above policy. Thanks, Brad ======================================================== Bradley Lowekamp Medical Science and Computing for Office of High Performance Computing and Communications National Library of Medicine [email protected]
_______________________________________________ Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Kitware offers ITK Training Courses, for more information visit: http://kitware.com/products/protraining.php Please keep messages on-topic and check the ITK FAQ at: http://www.itk.org/Wiki/ITK_FAQ Follow this link to subscribe/unsubscribe: http://www.itk.org/mailman/listinfo/insight-developers
