-
Notifications
You must be signed in to change notification settings - Fork 36
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.
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
0.16.0 release #952
Comments
I'm fine with waiting for Rust 0.39.0. I think it's better to pack a lot of breaking changes to align with py-polars in one or two releases than splitting them across many releases. |
I agree, but it's too huge and tedious work... |
The release notes have become too long and I will immediately release 0.16.0 when the next release of Rust Polars is made. |
It looks like there will be no Rust Polars release this week. (Since Python has been released) |
I don't think there's a link between the two, rust-polars 0.38 was released at the same time as py-polars 0.20.13. A lot of bugs related to the new string type have been fixed now, but they have fully rewritten the way expressions are cached so they might take a week or two to fix some critical bugs related to that before releasing 0.39 (just guessing of course). |
Hmmm, looks like it was just released. #1034 |
Thanks, I have a couple of things I'm considering doing to follow up for #1034.
|
I believe the changes on the Rust side are complete, so I have triggered a library release. |
0.16.0 has been released in #1041 |
The main branch currently contains a large number of breaking changes to bring its behavior consistent with that of Python Polars.
On the other hand, there are very few changes on the Rust side.
If there are no further comments, I would like to delay the release of 0.16.0 until Rust 0.39.x is released, and do further breaking refactoring before then.
The text was updated successfully, but these errors were encountered: