You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, when working on a new release the team maintaining CKAN have in mind questions like:
Is this change going to break current installations?
Can we provide a backwards compatibility?
How easy is gonna be for current implementations to migrate to this new release?
How is this going to impact on the effort of current CKAN projects to keep using CKAN?
Is this a breaking change that will be easy to transition to?
Or is this a breaking change that will push the community away given that it is not worthy to implement?
What about all the current instances of CKAN? Do they have the adequate resources/support to migrate to this new version?
However, breaking changes are sometimes necessary to be able to integrate newer technologies, improve the basecode or make the software more maintainable. CKAN 3.0 will inevitably include some breaking changes so the main goal of this conversation is to define, and gather feedback about the limits and scopes of the breaking changes of the new version.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
About
Usually, when working on a new release the team maintaining CKAN have in mind questions like:
However, breaking changes are sometimes necessary to be able to integrate newer technologies, improve the basecode or make the software more maintainable. CKAN 3.0 will inevitably include some breaking changes so the main goal of this conversation is to define, and gather feedback about the limits and scopes of the breaking changes of the new version.
Beta Was this translation helpful? Give feedback.
All reactions