vbarua commented on PR #1399: URL: https://github.com/apache/arrow-go/pull/1399#issuecomment-6642058860
> happy to move forward with this once we have a stable tag instead of the alpha one. For this PR, we just published the first official v9 release: https://pkg.go.dev/github.com/substrait-io/substrait-go/v9 @kadinrabo was checking that the alpha build compiled correctly for arrow-go before we published it. He's updated this to use the official release. > Why does substrait-go do so many breaking changes and major version updates? 😦 Honestly, because we accidentally published the first v1 release before the library should have been considered stable, and we never put the cat back in the bag. If the constant major updates are becoming a problem, we can consider starting fresh with a new name to limit these issues in the future. > We should probably use aliases or other changes in here to hide the public substrait types from the arrow-go public API to avoid these in the future. Would it make sense to add the aliases in this PR if this is going to be breaking already? It would probably be good the decouple the arrow-go API from the substrait-go one. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
