Repository navigation
[Release] Prepare ray-doris 1.3 for Ray 2.59.0 - #11
Merged
Merged
Conversation
Signed-off-by: jiangxt2 <[email protected]>
|
Validate candidate version derivation and its use in release operations. Signed-off-by: jiangxt2 <[email protected]>
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
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.
Description
Prepare ray-doris 1.3 as the formal candidate and align pyproject.toml, the public version, README, and versioned release notes. The notes document the final Ray 2.59.x compatibility range and its Doris validation profile. The connector's read/write behavior and maturity classifications remain unchanged.
Related issues
Closes #10.
How tested
Additional information
The change does not alter function signatures, Doris execution semantics, Ray retry behavior, or the existing maturity level. The release notes describe the Ray 2.59.0 compatibility evidence and the standard versus enterprise evidence boundary.