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

Krisztian Szucs commented on ARROW-13083:
-----------------------------------------

Tested this out locally, the version is properly generated after placing 
{{apache-arrow-5.0.0.dev}} tag on master. 
Pushed the tag upstream: 
https://github.com/apache/arrow/releases/tag/apache-arrow-5.0.0.dev
Also updated the release management guide to create a tag after the version 
bumps: 
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-Post-releasetasks

> [Python] Wrong SCM version detection both in setup.py and crossbow
> ------------------------------------------------------------------
>
>                 Key: ARROW-13083
>                 URL: https://issues.apache.org/jira/browse/ARROW-13083
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>            Reporter: Krisztian Szucs
>            Assignee: Krisztian Szucs
>            Priority: Major
>
> Wanted to install nightly wheels for a rust integration test when I noticed 
> that the nightly wheels get produced with base version 3.0.0.
> This is due to the recently changed release workflow. Now we're creating tags 
> from release branches without a post rebase step, so setuptools_scm fails to 
> find the correct version number on diverged branches.



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

Reply via email to