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

Release checklist #101

Open
5 of 6 tasks
RAMitchell opened this issue Apr 12, 2024 · 4 comments
Open
5 of 6 tasks

Release checklist #101

RAMitchell opened this issue Apr 12, 2024 · 4 comments
Assignees

Comments

@RAMitchell
Copy link
Contributor

RAMitchell commented Apr 12, 2024

The following is a list of tasks for us to make a legate-boost single-node release.

  • Legate.core.internal and cunumeric.internal conda packages
  • SWIPAT to open source legate-boost
  • Adopt versioning for legate-boost (Implement calendar versioning #162)
  • Conda package for legate-boost (add legate-boost conda packages #115)
  • Documentation is publically available
  • publish a stable release (v24.09.00) once there are stable legate and cunumeric 24.09 releases

This first release will target a single node user being able to install:

conda install -c some-channel legate-core cunumeric legate-boost

and run basic legateboost examples on multiple GPUs or CPUs. They should be able to read documention for python API functions.

@aterrel
Copy link

aterrel commented Apr 15, 2024

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?

@sbuneti
Copy link

sbuneti commented Apr 22, 2024

@manopapad for cuNumeric & Legate.core packaging strategy/updates

@jameslamb
Copy link
Member

Adopt versioning for legate-boost

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 main as v0.1.0: https://github.com/rapidsai/legate-boost/releases/tag/v0.1.0. The first calendar-based version after that (v2024.09.00, presumably) will then be newer than that.

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 24.09.00dev{n}, where {n} is "number of commits since the previous stable release (indicated by git tags)".

@jameslamb
Copy link
Member

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 legate-boost (24.09.00) whenever there are stable releases of legate and cunumeric.

There are not any yet:

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

No branches or pull requests

4 participants