redhat-developer/app-services-sdk-go

Introduce go submodules to use independent versioning

Closed this issue · 4 comments

wtrocki commented

For projects that use multiple SDK sometimes we need to update one and stay with old version of the other.

Imagine scenario:
v0.5.0

  • kafka-mgmt
  • registry-mgmt

Now we want received 2 changes for those apis independently but only want to use registry change.
Users should be able to import SDK's individually with different versions

  • kafka-mgmt 0.5.1
  • registry-mgmt 0.5.0
wtrocki commented

I think CLI should use individual imports rather than entire SDK. Releases should be the same

craicoverflow commented

I am going to pick up this now. This has caused many headaches already so it would be good to have it done soon.

craicoverflow commented

Releases should be the same

I don't know whether I agree with this. What would be the main reasoning for this? You could end up in a situation where a less active API has had 0 changes between dozens of releases. This would also mean we could be creating minor releases with no new features added, which goes against SemVer and would also lead to some confusion by consumers.

wtrocki commented

I don't know whether I agree with this

You are right. This comment was old and outdated.
Submodules force different release format