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.

Sign up for GitHub

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

RSN for conda package legacy labelling #570

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

RSN for conda package legacy labelling #570

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e20ea8c
Add notice for conda package `legacy` labelling
gforsyth Jan 27, 2025
e5bbcc6
Update _notices/rsn0042.md
gforsyth Jan 28, 2025
ba89cba
Use correct label command
gforsyth Jan 28, 2025
844022d
Update _notices/rsn0042.md
gforsyth Jan 28, 2025
2417de8
Remove blank line
bdice Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
61 changes: 61 additions & 0 deletions _notices/rsn0042.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
---
layout: notice
parent: RAPIDS Support Notices
grand_parent: RAPIDS Notices
nav_exclude: true
notice_type: rsn
# Update meta-data for notice
notice_id: 42 # should match notice number
notice_pin: true # set to true to pin to notice page

title: "Moving older RAPIDS conda packages to a `legacy` label"
notice_author: RAPIDS Ops
notice_status: Proposal
notice_status_color: blue
# 'notice_status' and 'notice_status_color' combinations:
# "Proposal" - "blue"
# "Completed" - "green"
# "Review" - "purple"
# "In Progress" - "yellow"
# "Closed" - "red"
notice_topic: Platform Support Change
notice_rapids_version: "<=v23.02"
notice_created: 2025-01-27
# 'notice_updated' should match 'notice_created' until an update is made
notice_updated: 2025-01-27
---

## Overview

RAPIDS will move certain older conda packages in the `rapidsai` conda channel
under a new label: `legacy`. These packages will still be available by adding
`-c rapidsai/label/legacy` to installation and search commands.

By moving these packages out of the main portion of the channel, newer RAPIDS
conda environments will be solvable with `channel_priority: strict`, speeding up

bdice marked this conversation as resolved.
Show resolved Hide resolved
environment solve times.

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`.
Copy link
Contributor

Choose a reason for hiding this comment

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

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.

Copy link
Author

Choose a reason for hiding this comment

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

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.

Copy link
Contributor

@bdice bdice Jan 28, 2025 •
edited
Loading

Choose a reason for hiding this comment

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

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.

Copy link
Author

Choose a reason for hiding this comment

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

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

Copy link
Contributor

Choose a reason for hiding this comment

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

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?

Copy link
Author

Choose a reason for hiding this comment

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

Yes



## Impact

RAPIDS environments installed using `conda` or `mamba`, for environments older
than RAPIDS `v23.04` will fail to install unless `-c rapidsai/label/legacy` is
added to the installation command.

e.g. if you are creating an environment like:

```python
mamba create -n rapids-23.02 rapids=23.02 python=3.10 'cuda-version>=11.4,<=11.8' -c rapidsai -c conda-forge -c nvidia
```

you will need to instead run

```python
mamba create -n rapids-23.02 rapids=23.02 python=3.10 'cuda-version>=11.4,<=11.8' -c rapidsai -c rapidsai/label/legacy -c conda-forge -c nvidia
```