[
https://issues.apache.org/jira/browse/ARROW-13083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364924#comment-17364924
]
Krisztian Szucs commented on ARROW-13083:
-----------------------------------------
Thanks for the suggestion [~jorisvandenbossche], that's a nice workaround! The
question is, shall we tag the fork point or the [commit where we
bump|https://github.com/apache/arrow/commit/aa28470ca2a901a80e88874b4341905a3188186f#diff-eb8b42d9346d0a5d371facf21a8bfa2d16fb49e213ae7c21f03863accebe0fcf]
the development versions?
> [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
> 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)
