You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Uwe L. Korn (JIRA)" <ji...@apache.org> on 2017/05/27 16:15:05 UTC

[jira] [Commented] (ARROW-979) [Python] Fix setuptools_scm version when release tag is not in the master timeline

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

Uwe L. Korn commented on ARROW-979:
-----------------------------------

This most simple fix for this would be to tag the first commit post-release on master with {{apache-arrow-0.4.0.post}}. This would restore {{setuptools_scm}} functionality again and we would be able to do releases off master.

[~wesmckinn] would that be ok with you?

[~julienledem] Is there any problem with doing non-release tags in git?

> [Python] Fix setuptools_scm version when release tag is not in the master timeline
> ----------------------------------------------------------------------------------
>
>                 Key: ARROW-979
>                 URL: https://issues.apache.org/jira/browse/ARROW-979
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Python
>            Reporter: Wes McKinney
>
> Independent of the discussion about the release branching process, SCM auto-versioning tools should not be dependent on finding a release tag in the timeline



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)