Open blakeromano opened 9 months ago
FWIW the contract between function SDKs and Crossplane is protobuf, and we intend to follow good forward/backward compatibility rules there. So in general:
That all said, I agree we should release SDKs to take advantage of new features and make it obvious what SDK versions support said features.
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale
because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
/fresh
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale
because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
/fresh
Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale
because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh
will mark this issue as not stale.
What problem are you facing?
When a new version of Crossplane is released new features may be added that the Function SDKs will need to be added to support. I also am unsure now how compatible X version of the Function SDK is with X version of Crossplane.
How could Crossplane help solve your problem?
A Version Compatibility Table should be created for the SDKs and when Crossplane is releasing a new version we should create a new version of the SDK.