kou opened a new issue, #7041:
URL: https://github.com/apache/arrow-rs/issues/7041

   **Is your feature request related to a problem or challenge? Please describe 
what you are trying to do.**
   
   GitHub has a feature that manages releases: GitHub releases: 
https://docs.github.com/en/repositories/releasing-projects-on-github
   
   All GitHub repositories have 
`https://github.com/${ORGANIZATION}/${REPOSITORY}/releases`. 
https://github.com/apache/arrow-rs/releases is for apache/arrow-rs.
   
   Many projects use the feature to show changes in a release, provide 
artifacts (e.g. source archive) and so on. If we use it like other projects, 
users may be easy to find changes in each release.
   
   **Describe the solution you'd like**
   
   We can create GitHub releases from existing our contents. For example, we 
can use existing `CHANGELOG.md` for changes in a release.
   
   It's not a big task but it's better that we automate it.
   
   **Describe alternatives you've considered**
   
   We can do it as a manual task in a release process. For example: 
https://github.com/apache/arrow-rs/pull/7031/files#diff-7b90af0d72004d8b923b4ed55f67a5f3e40e6a08ec9637f382d6506dd309848dR204
   
   `````markdown
   ### Create a GitHub release
   
   Run a command such as the following to create a GitHub release from the tag:
   
   ```shell
   git checkout 4.1.0
   gh release create 4.1.0 --title 4.1.0 --notes-file CHANGELOG.md
   ```
   `````
   
   **Additional context**
   
   Other Arrow projects such as ADBC and arrow-go use GitHub releases:
   * https://github.com/apache/arrow-adbc/releases
   * https://github.com/apache/arrow-go/releases
   
   See also: 
https://github.com/apache/arrow-rs/issues/6929#issuecomment-2616428001 and 
related comments in the issue.


-- 
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]

Reply via email to