DOC: Start ITK 6 migration guide#4695
Merged
thewtex merged 1 commit intoInsightSoftwareConsortium:masterfrom May 29, 2024
Merged
DOC: Start ITK 6 migration guide#4695thewtex merged 1 commit intoInsightSoftwareConsortium:masterfrom
thewtex merged 1 commit intoInsightSoftwareConsortium:masterfrom
Conversation
This document provides information for developers on how to migrate from ITK 5 to ITK 6. It contains information on what backwards-incompatible changes were made, such as the removal of deprecated code, why they made, and how to migrate old code no the new code. Developers making backwards-incompatible changes for ITK 6 should add entries to this document as the changes are made. The ITK 6 migration guide is similar to the ITK 5 migration guide with the following modifications: - The current and previous migration guide are now developed on GitHub and published to the ITK Sphinx Documentation. - We now have the consistent and simpler ITK_LEGACY_REMOVE and ITK_FUTURE_LEGACY_REMOVE options without the additional *_COMPATIBILITY option. - We have "most" instead of "all" ITK_LEGACY_REMOVE, ITK_FUTURE_LEGACY_REMOVE to allow for exceptions on an as-needed basis to prevent forcing deprecations that may be premature in terms of their removal-cost-benefit or the availability of migration options.
dzenanz
approved these changes
May 28, 2024
seanm
approved these changes
May 28, 2024
phcerdan
approved these changes
May 28, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This document provides information for developers on how to migrate from
ITK 5 to ITK 6. It contains information on what backwards-incompatible
changes were made, such as the removal of deprecated code, why they made,
and how to migrate old code no the new code.
Developers making backwards-incompatible changes for ITK 6 should add
entries to this document as the changes are made.
The ITK 6 migration guide is similar to the ITK 5 migration guide with the
following modifications:
and published to the ITK Sphinx Documentation.
ITK_FUTURE_LEGACY_REMOVE options without the additional
*_COMPATIBILITY option.
ITK_FUTURE_LEGACY_REMOVE to allow for exceptions on an as-needed basis
to prevent forcing deprecations that may be premature in terms of
their removal-cost-benefit or the availability of migration
options.