nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Backwards Compatibility Strategy

dan1

Hi,

I didn't find anything about backwards compatibility in neither the FAQ nor the user's guide. Is the strategy documented somewhere? I found a few posts that mentioned backwards compatibility. Here is the main one…

Activiti is stable as it gets. All API's defined since 5.0 are guaranteed not to change. If needed, we introduce backwards compatibility and deprecation strategies with clear documentation.

If an API were to marked as deprecated, how long would it continue to be supported? Is that measured in terms of years, or number of releases, or are such things decided on a case by case basis?

Thanks,
Dan

Find more posts tagged with

Comments

jbarrez

The general rule of thumb is that, when we deprecate something, we give it two releases before we remove it. And indeed, when we do it, we make sure there is a compatible way (note: this doesn't mean some small code changes would be needed) to achieve similar functionality.