topic Re: Backwards Compatibility Strategy in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/backwards-compatibility-strategy/m-p/133036#M93445 <HTML><HEAD></HEAD><BODY><SPAN>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.</SPAN></BODY></HTML> Tue, 11 Dec 2012 07:19:23 GMT jbarrez 2012-12-11T07:19:23Z Backwards Compatibility Strategy https://connect.hyland.com/t5/alfresco-archive/backwards-compatibility-strategy/m-p/133035#M93444 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 cha Mon, 10 Dec 2012 14:57:45 GMT https://connect.hyland.com/t5/alfresco-archive/backwards-compatibility-strategy/m-p/133035#M93444 dan1 2012-12-10T14:57:45Z Re: Backwards Compatibility Strategy https://connect.hyland.com/t5/alfresco-archive/backwards-compatibility-strategy/m-p/133036#M93445 <HTML><HEAD></HEAD><BODY><SPAN>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.</SPAN></BODY></HTML> Tue, 11 Dec 2012 07:19:23 GMT https://connect.hyland.com/t5/alfresco-archive/backwards-compatibility-strategy/m-p/133036#M93445 jbarrez 2012-12-11T07:19:23Z