[
https://issues.apache.org/jira/browse/ARROW-13083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364930#comment-17364930
]
Joris Van den Bossche commented on ARROW-13083:
-----------------------------------------------
But if we want to be pedantic, then the version bump commit should be the first
commit after the branching point ;-)
(so I would personally not be too pedantic and tie the tag to the version bump
commit, which seems most logical to me, and just try to do it not too far after
the branching point)
> [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)
