We discussed at the UG that some features might become non-forward compatible in the future. While it is our tasks as member of the UG to ensure that this is as limited as possible, we know that it is likely to happen.
What would be considered the best solution on how to address this?
Offered suggestion from User Group participant:- Always ensure to keep forward compatibility on minor increase of CDB Changes (from CDB 3.0 to 3.1, to 3.2Ã¢â¬Â¦). This could be done by continuing to support the previous specification definition but would suggest user to move to the new definition. When we go to a major revision change: from 3.x to 4.0, we would then remove the support to the previous functionalities.
If you have any additional suggestion or improvement on the current suggestion, we invite you to please participate and share your comments on this posting.