[ 
https://issues.apache.org/jira/browse/ARROW-9014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated ARROW-9014:
----------------------------------
    Labels: pull-request-available  (was: )

> [Packaging] Bump the minor part of the automatically generated version in 
> crossbow
> ----------------------------------------------------------------------------------
>
>                 Key: ARROW-9014
>                 URL: https://issues.apache.org/jira/browse/ARROW-9014
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Packaging, Python
>            Reporter: Krisztian Szucs
>            Assignee: Krisztian Szucs
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Crossbow uses setuptools_scm to generate a development version number using 
> git describe command. This means that it finds the latest {{reachable}} tag 
> from the current commit on master. 
> The minor releases are created from the master branch whereas the patch 
> release tags point to commits on maintenance branches (like 0.17.x) which 
> means that if we already have released a patch version, like 0.17.1 then 
> crossbow generates a version number like 
> 0.17.0.dev{number-of-commits-from-0.17.0} and bumps its patch tag, eventually 
> creating binary packages with version 0.17.1.dev123.
> The main problem with this is that the produced nightly python wheels are not 
> picked up by pip, because on pypi we already have that patch release 
> available and pip doesn't consider 0.17.1.dev123 newer than 0.17.1 (with 
> --pre option passed). 
> So to force pip to install the newer nightly packages we need to bump the 
> minor version instead. 



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

Reply via email to