Hey all, There was a request to backport a fix for Go Arrow from v13 back to v12 [1] to improve a dependency situation for a user of Go Arrow where the databricks-sql-go driver is using Arrow v12 currently, thus exhibiting the bug they want to backport a fix for. To be fair, they have also made a request for databricks to simply update their version of Arrow [2].
Since Go only requires a git tag to "release" rather than any binary artifact results, in the past we've done a patch release for Go by simply creating the tag and uploading the source tarball [3] significantly reducing the cost of performing the release itself. Assuming a vote passes, I wanted to take a pulse on opinions as to backporting and releasing a v12.0.2 for Go and if anyone would oppose such a thing. Thanks everyone! --Matt [1]: https://github.com/apache/arrow/issues/41156 [2]: https://github.com/databricks/databricks-sql-go/pull/216 [3]: https://lists.apache.org/thread/lt8dp0dxtcvkkz7k6wyhdjcwb5yzbvll
