RSN for conda package legacy labelling
#570
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
✅ Deploy Preview for docs-rapids-ai ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
def31c7 to
e20ea8c
Compare
_notices/rsn0042.md
Outdated
|
|
||
| RAPIDS will move certain older conda packages in the `rapidsai` conda channel | ||
| under a new label: `legacy`. These packages will still be available by appending | ||
| `--label legacy` to installation and search commands. |
There was a problem hiding this comment.
I'm a little unclear on this. It looks like --label is used when uploading, but for users to install, they need something like --channel rapidsai --channel rapidsai/label/legacy. Does that sound correct?
There was a problem hiding this comment.
Yup, thanks for catching that @bdice !
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
| All RAPIDS conda install commands for RAPIDS versions `v23.04+` will continue to | ||
| work without any user intervention. | ||
|
|
||
| This change will occur concurrently with the release of RAPIDS `v25.04`. |
There was a problem hiding this comment.
Just checking: We will be able to test strict channel priority in our CI before the 25.04 release, right? I want to be sure we minimize the risk of breaking recent releases (25.02 / 25.04) during this change.
There was a problem hiding this comment.
We'll be able to test 25.02 once all of those packages are released using the same method I tested the previous releases with. Regarding 25.04, we can also release all of those packages, test, then move the selected older packages under the legacy label, or we can move them under the label, see if it works, and then undo the labeling if it breaks.
If 25.02 works, I'd feel confident moving the packages straight to the label for 25.04, and that would let us accurately advertise strict channel priority for the new install instructions.
There was a problem hiding this comment.
That's helpful. What about enabling strict priority in our CI for PR & nightly builds/tests, though? It sounds like you're discussing the user experience that we expect after the release is complete.
There was a problem hiding this comment.
We can't really enable them for CI until we move the older packages under legacy. The conda-metachannel package is quite brittle at this point and I don't think we want that spun up as part of our CI
There was a problem hiding this comment.
Does that mean we will make the legacy label along with the 25.04 release, and then enable strict priority in our CI during development for 25.06?
Co-authored-by: Bradley Dice <bdice@bradleydice.com>
RSN for moving select conda packages behind a new
legacylabel concurrent with thev25.04release.I wasn't sure whether to note the
notice_rapids_versionas the version wherethis change takes place (
25.04) or the versions impacted by the change(
<=23.02). I think<=23.02makes more sense and I've written it as such, buthappy to change things around.
xref rapidsai/build-planning#84