Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ARROW-9014: [Packaging] Bump the minor part of the automatically generated version in crossbow #7327

Closed
wants to merge 3 commits into from

Conversation

kszucs
Copy link
Member

@kszucs kszucs commented Jun 2, 2020

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.

@kszucs
Copy link
Member Author

kszucs commented Jun 2, 2020

@github-actions crossbow submit wheel-manylinux1-cp36m

@kszucs
Copy link
Member Author

kszucs commented Jun 2, 2020

The produced wheel should have version number: 0.18.0.dev{distance}

@github-actions
Copy link

github-actions bot commented Jun 2, 2020

Revision: 838509c

Submitted crossbow builds: ursa-labs/crossbow @ actions-281

Task Status
wheel-manylinux1-cp36m Azure

@github-actions
Copy link

github-actions bot commented Jun 2, 2020

dev/tasks/crossbow.py Outdated Show resolved Hide resolved
major, minor, patch = map(int, match.groups())

# the bumped version number after 0.17.x will be 0.18.0.dev300
return "{}.{}.{}.dev{}".format(major, minor + 1, patch, version.distance)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you sure patch is 0 here? Otherwise you could get e.g. 0.18.1.dev300.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since the packaging builds are executed from the master branch we should have patch equal to zero.

Copy link
Member Author

@kszucs kszucs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants