Skip to content

Clarify API deprecation policy #65093

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

Merged
bveeramani merged 2 commits into from
Jul 29, 2026
Merged

Clarify API deprecation policy #65093

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bd4e1aa
Initial commit
bveeramani Jul 28, 2026
3869f70
Address review comment
bveeramani Jul 29, 2026
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
6 changes: 3 additions & 3 deletions doc/source/ray-contribute/api-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,13 +69,13 @@ Users have high expectations for certain exposure levels, so we need to be cauti
- No
- Yes
* - Can this API be demoted to a lower level? If so then how?
- Can be demoted to Deprecated only. The API should emit warning messages and a deadline for deprecations in **six months (or +25 Ray minor versions)**.
- Can be demoted to Deprecated only. The API should emit warning messages and a deadline for deprecations in **three months (or +12 Ray minor versions)**.
- Can be demoted to Deprecated only. The API should emit warning messages and a deadline for deprecations in **six months or +25 Ray minor versions, whichever comes first**.
- Can be demoted to Deprecated only. The API should emit warning messages and a deadline for deprecations in **three months or +12 Ray minor versions, whichever comes first**.
- Users must allow for and expect breaking changes in alpha components, and must have no expectations of stability.
- Yes
- No annotations mean it is a developer API by default
* - Can you remove or change this API's parameters?
- Yes. The API should emit warning messages and you must set a deadline for the end-of-life of the original version that is **six months or +25 Ray minor versions**. During the transition period, you must support both the new and old parameters.
- Yes. The API should emit warning messages and you must set a deadline for the end-of-life of the original version that is **six months or +25 Ray minor versions, whichever comes first**. During the transition period, you must support both the new and old parameters.
Comment thread
bveeramani marked this conversation as resolved.
- Yes. The API should emit warning messages and you must set a deadline for the change in **three months or +12 Ray minor versions**. During the transition period, you must support both the new and old parameters.
- Users must allow for and expect breaking changes in alpha components, and must have no expectations of stability.
- No
Expand Down
Loading