-
Notifications
You must be signed in to change notification settings - Fork 517
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.4.20 release planning #674
Comments
This doesn't fix all the issues, because this crate still depends on chrono 0.4.19, which as a potential segfault. But there's no newer version of chrono yet. See chronotope/chrono#674 for discussion of the 0.4.20 release.
This doesn't fix all the issues, because this crate still depends on chrono 0.4.19, which as a potential segfault. But there's no newer version of chrono yet. See chronotope/chrono#674 for discussion of the 0.4.20 release.
I notice that version 0.4.19 is using version 0.1.43 of the time crate. I noticed https://rustsec.org/advisories/RUSTSEC-2020-0071 today via |
Any info when the new version will be released? |
I guess we can release it at any time and make further compatible changes later. Let's get a beta or rc out first (see #676) so we can get some more testing before we push this out to the rest of the world. |
Is there a preferred way to track and provide feedback for the beta release? I am interested in helping to get the beta into an official release. |
I've published 0.4.20-beta.1 to crates.io, would be happy to get everyone to test it! |
Thanks @djc and chrono maintainers! |
I've published an rc.1 and written up some release notes for it: https://github.com/chronotope/chrono/releases/tag/v0.4.20-rc.1. Please let me know if anything is missing/unclear (@esheppa would especially value your feedback on the release notes). |
@djc - the release notes look great! (However they made me realize that I probably need to document the behavior of the caching of the tzfile data) Potentially we could add the following: |
0.4.20 has been released! |
databend has switched it's chrono's stream back to chronotope/chrono in datafuselabs/databend#6928. No build failure, no tests broken, no performance regression. I believe this version is good for everyone to upgrade. Nice work @djc! |
Currently to build downstream packages for targets emscripten, I clone a fork of chrono with #593 backported onto v0.4.19 and patch the downstream package's
Cargo.toml
by addingI am looking forward to not having to do this.
The text was updated successfully, but these errors were encountered: