[ 
https://issues.apache.org/jira/browse/ARROW-12701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385759#comment-17385759
 ] 

Andrew Lamb commented on ARROW-12701:
-------------------------------------

Thanks for doing this [~thisisnic] -- the releases in the  arrow-rs repo are 
git "tags" -- so the list is here: https://github.com/apache/arrow-rs/tags (not 
the branches)

The `active_release` branch is something used while creating releases rather 
than a release itself

If you want to compute the difference between the 4.0.0 release and the 5.0.0 
release, for example, you can find it with a command such as

{code}
# in an arrow-rs checkout
(arrow_dev) alamb@MacBook-Pro:~/Software/arrow-rs$ git shortlog -sn 4.0.0..5.0.0
{code}

Which is how I created the list for the rust blog post: 
https://github.com/apache/arrow-site/pull/128



> [Website][Release] Include Rust and DataFusion commits, contributors, changes 
> in release notes
> ----------------------------------------------------------------------------------------------
>
>                 Key: ARROW-12701
>                 URL: https://issues.apache.org/jira/browse/ARROW-12701
>             Project: Apache Arrow
>          Issue Type: Task
>          Components: Website
>            Reporter: Ian Cook
>            Assignee: Nic Crane
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 5.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> For the 5.0.0 release, we should change the code in 
> {{dev/releasepost-03-website.sh}} to include commits, contributors, and 
> changes to the official {{apache/arrow-rs}} and {{apache/arrow-datafusion}} 
> repos. This is import to ensure that the contributions to Rust, DataFusion, 
> and Ballista are recognized in our release notes and blog posts going forward.
> [~alamb] [~andygrove] [~Dandandan] [~jorgecarleitao] could one of you take 
> this on? Thank you



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to