ITK/Backward Compatibility Open Discussion: Difference between revisions

From KitwarePublic
< ITK
Jump to navigationJump to search
Line 9: Line 9:
= Discussion Topics =
= Discussion Topics =


* Deprecation of classes / method. When to deprecate, and how to deprecate.
# Deprecation of classes / method. When to deprecate, and how to deprecate.
* Drawing the line where fixing a bug will result in backward compatibility breaks.
# Drawing the line where fixing a bug will result in backward compatibility breaks.
* Cathedral/Bazar: How much burden to put on new contributions to the toolkit.  
# Cathedral/Bazar: How much burden to put on new contributions to the toolkit.  
** Is the Insight Journal + Code Review directory a process that is too burdensome.
## Is the Insight Journal + Code Review directory a process that is too burdensome.
* When can we require additional effort from users to update their code for using new versions of ITK ?
# When can we require additional effort from users to update their code for using new versions of ITK ?
** Never
## Never
** Once a year
## Once a year
** Once every five years
## Once every five years
* How far back in time should we maintain backward compatibility (relates to the previous topic)
# How far back in time should we maintain backward compatibility (relates to the previous topic)
** Today's version should be compatible with ITK version from N years ago
## Today's version should be compatible with ITK version from N years ago
*** 1 year ?
### 1 year ?
*** 2 years ?
### 2 years ?
*** 5 years ?
### 5 years ?


= Position Statement 1 (Luis Ibanez)=
= Position Statement 1 (Luis Ibanez)=

Revision as of 12:53, 6 May 2008

The topic of backward compatibility has generated animated discussions among users and developers.

We gather here multiple points of view from some of the influential users and developers.

The content of this page is not intended to be conclusive on any of the proposed topics. It simple intends to gather elements of discussion that will serve as food-for-thought.

Main Discussion Topics

Discussion Topics

  1. Deprecation of classes / method. When to deprecate, and how to deprecate.
  2. Drawing the line where fixing a bug will result in backward compatibility breaks.
  3. Cathedral/Bazar: How much burden to put on new contributions to the toolkit.
    1. Is the Insight Journal + Code Review directory a process that is too burdensome.
  4. When can we require additional effort from users to update their code for using new versions of ITK ?
    1. Never
    2. Once a year
    3. Once every five years
  5. How far back in time should we maintain backward compatibility (relates to the previous topic)
    1. Today's version should be compatible with ITK version from N years ago
      1. 1 year ?
      2. 2 years ?
      3. 5 years ?

Position Statement 1 (Luis Ibanez)

Topic A

Topic B

Topic C

Position Statement 2 (Bill Lorensen)

Topic A

Topic B

Topic C

Position Statement 3 (Steve Pieper)

Topic A

Topic B

Topic C

Position Statement 4

Topic A

Topic B

Topic C

Position Statement 5

Topic A

Topic B

Topic C

Retrieved from "https://public.kitware.com/Wiki/index.php?title=ITK/Backward_Compatibility_Open_Discussion&oldid=12252"