Update versioning strategy

[vyasr]

See rapidsai/rmm#1347

[pentschev]

@vyasr left a few questions regarding the discrepancy in RAPIDS and UCX-Py versions, not sure if they're being addressed externally or if we need extra steps here to get the proper UCX-Py version.

[pentschev]

@vyasr I see you've updated the release script in 3ee156e . I'm assuming now that rapids-generate-version and RAPIDS_PACKAGE_VERSION will pick up the version that was actually set via the release script, is that correct or are there other changes needed here still?

[vyasr]

@vyasr I see you've updated the release script in 3ee156e . I'm assuming now that rapids-generate-version and RAPIDS_PACKAGE_VERSION will pick up the version that was actually set via the release script, is that correct or are there other changes needed here still?

No and yes 🙂

• No because the versions are based on the tags on the repo, not the version contained in _version.py
• Yes that we're good without needing further changes because it's tag-based.

[pentschev]

LGTM, thanks @vyasr !

[pentschev]

BTW, the RTD failure is being addressed by #999 .

[vyasr]

Great, thanks! Let's hold off merging for the moment (as per the label), we have PRs like this open across RAPIDS and in case any additional good feedback comes in on one of them we'll want to apply it consistently to the other repos too.

[vyasr]

/merge