vishesh92 commented on PR #77: URL: https://github.com/apache/cloudstack-go/pull/77#issuecomment-1976261911
If someone upgrades their cloudstack-go SDK and builds their project, the build will fail only if some method which is now changed is being used. Any good IDE should be able to list down the parts of code where a change needs to be done. IMO, we should mention the methods in the release notes instead of ensuring backward compatibility for cloudstack-go. Another alternative approach I can think of is generating multiple modules as per the ACS version. Every release of cloudstack-go will have multiple modules for different ACS versions which are being supported at the time. (e.g. 4.18, 4.19, etc.). We can ignore minor version for this and ensure that we are backward compatible for all major versions. This would still require a code change, but can be easily done my a simple "Find & Replace" of the module. e.g. `"github.com/apache/cloudstack-go/v2/cloudstack"` will need to be replaced with `"github.com/apache/cloudstack-go/v2/cloudstack/4.19"` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
