[Insight-developers] Modularization Schedule

Brad King brad.king at kitware.com
Tue Mar 8 09:55:26 EST 2011


On 03/08/2011 08:56 AM, Bradley Lowekamp wrote:
> I could merge my patch. However, my patch is CMakeLists related, and
> that needs to be manually migrated to the new modular testing framework.
> So, I don't want to merge the patch because they may miss this change as
> they have already visited the file.

The modularization transition will consist of 3 commits:

(1) Remove all CMake build files that are not needed in modular ITK
(2) Bulk rename commit moving all remaining files to their new location
    but making zero changes to them
(3) Add modular ITK build files and modify any old build files that
    were moved as necessary

This will be scripted on top of the latest 'master' on the day we do the
transition.  Originally this was going to be late last week but we had
forgotten that the modular ITK had been using 4 month old snapshots of
the Utilities directory.  Now Xiaoxiao is working on making the manifest
map all those directories too so that we don't rewind them to old versions
when doing the transition commits.

Changes to CMake code will likely be dropped by commit (1) because most
of the build system is new in commit (3).

Changes to existing C++ files should still be okay while we prepare the
transition scripts.  It's only adding new files that we'd like to avoid
so that the manifest that maps the files does not get out of date.

-Brad K


More information about the Insight-developers mailing list