Re: How to handle compability between version releases

Dave Mertens wrote:

For a new customer i need to redesign the Payment_Clieop API. This because currently it's only possible to either send a creditor batch or a payment batch. The new customer requires a clieop which do both batches at the same time. Version 1.0 is already released on the pear site. Do i have to keep compability between those versions? I can create a work around that simulates most of the current API. A few calls have to be changed and the include file will get another name. If you think that the changes could helpful to other users, then try to keep compatability and release a new version with the changes, but if the change will only really benefit your client, then just make it a local change to the code, and don't bother releasing it, I guess it's just a case of working out whether other users would want the ability to do that or not.

Jon