sgilmore10 opened a new pull request, #40956: URL: https://github.com/apache/arrow/pull/40956
### Rationale for this change This is a follow up to https://github.com/apache/arrow/pull/38660 and [this mailing list discussion](https://lists.apache.org/thread/0xyow40h7b1bptsppb0rxd4g9r1xpmh6). We would like to upload the MLTBX packages for the MATLAB bindings to the GitHub Releases area for the Apache Arrow GitHub project. Using GitHub Releases will enable tight integration with the [MathWorks File Exchange](https://www.mathworks.com/matlabcentral/fileexchange), which should make it easy for users to discover and install the MATLAB interface using MATLAB. To make this possible, we need to update the release scripts under [/dev/release](https://github.com/apache/arrow/tree/main/dev/release) to upload the MLTBX packages built by crossbow to the GitHub Releases area. ### What changes are included in this PR? 1. Modified `dev/release/05-binary-upload.sh` to sign and upload release candidate MLTBX files to apache/arrow's GitHub Releases Area using the [`gh release create`](https://cli.github.com/manual/gh_release_create) command. 2. Marked the created GitHub Release as a `prerelease` to differentiate between release candidates and official releases. 3. Compared the format of the created GitHub Releases to the format of [apache/arrow-flight-sql-postgresql's](https://github.com/apache/arrow-flight-sql-postgresql/releases) GitHub Releases to validate our changes made sense. ### Are these changes tested? I was not able to run `dev/release/05-binary-upload.sh` directly, but I did test the `gh create release`, `gpg`, and `shasum` commands worked as expected by creating a "dummy" release for this repository: `https://github.com/sgilmore10/TestRepo/releases/tag/1.0.0rc1` ### Are there any user-facing changes? No. ### Future Directions 1. Modify `dev/release/post-02-upload.sh` to create a non-prerelease GitHub Release for the MATLAB bindings. 2. Create an Apache Arrow entry on the MathWorks File Exchange to facilitate a one-click install workflow for the MATLAB bindings. 6. Refactor the changes made to `05-binary-upload.sh` into a separate function that can be reused by `post-02-upload.sh` to reduce code duplication. ### Open Questions 1. Should we include the list of issues resolved in the release notes for prereleases? 2. @kou, @assignUser, or @raulcd, do you have suggestions on how we can validate the changes to `dev/release/05-binary-upload.sh`? -- 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]
