Clarify API deprecation policy - #65093
Merged
Merged
Conversation
Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the API policy documentation to clarify deprecation and parameter change deadlines by adding the phrase "whichever comes first". A review comment suggests also updating the Beta Public APIs policy on line 79 to include "whichever comes first" for consistency.
elliot-barn
approved these changes
Jul 28, 2026
dstrodtman
added
go
dstrodtman
approved these changes
Jul 28, 2026
dstrodtman
left a comment
dstrodtman
left a comment
Contributor
There was a problem hiding this comment.
stamped.
docs-go label means tests should pass quickly (<20 minutes for now, trying to get faster), even with an edit.
ray-gardener
Bot
added
docs
Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
bveeramani
enabled auto-merge (squash)
July 29, 2026 21:08
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Our current API deprecation policy states that we can deprecate APIs after six months or 25 Ray minor releases. The problem is that it's unclear whether the six months or 25 minor releases takes precedence if we don't release weekly. For example, if we release every month, 25 minor releases is 2+ years.
To resolve this ambiguity, I'm clarifying that the policy is "Six months or 25 Ray minor releases, whichever comes first"