-
Notifications
You must be signed in to change notification settings - Fork 8
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
Release checklist #101
Comments
Met with @magnatelee, @RAMitchell, @mmccarty, @dongb It seems that it will be too quick of a turnaround to get legate.core released before ISC. @mmccarty mentioned that we could release a download without conda packages but if we release legate-boost without releasing the legate.core then users can be confused due to the python implementation being incompatible. Could we release a private version to share with partners? |
@manopapad for cuNumeric & Legate.core packaging strategy/updates |
We're going to adopt calendar-based versioning following what cuNumeric and Legate are doing as closely as possible. To help with that, I just tagged the latest commit on Having a tag in the repo is necessary for publishing pre-releases, because for those we'll follow the cuNumeric/Legate approach of using versions like |
Now that #115 is complete, most of this is done! I added one more item in the list at the top... we'll just want to cut a stable release of There are not any yet: |
The following is a list of tasks for us to make a legate-boost single-node release.
legate
andcunumeric
24.09 releasesThis first release will target a single node user being able to install:
and run basic legateboost examples on multiple GPUs or CPUs. They should be able to read documention for python API functions.
The text was updated successfully, but these errors were encountered: