From 77f23b7ed4817d08f29a0e5712ddf27e26c74f1b Mon Sep 17 00:00:00 2001 From: Bradlee Speice Date: Sun, 24 Jun 2018 23:59:33 -0400 Subject: [PATCH] Update reference to chrono version --- _posts/2018-06-25-dateutil-parser-to-rust.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2018-06-25-dateutil-parser-to-rust.md b/_posts/2018-06-25-dateutil-parser-to-rust.md index 9b366e4..c60e7e0 100644 --- a/_posts/2018-06-25-dateutil-parser-to-rust.md +++ b/_posts/2018-06-25-dateutil-parser-to-rust.md @@ -120,7 +120,7 @@ to figure out if the library I'm look at is dead or just stable. And even when the "canonical library" exists, there's no guarantees that it will be well-maintained. [Chrono](https://github.com/chronotope/chrono) is the *de facto* date/time library in Rust, -and just released version 0.4.3 like two weeks ago. Meanwhile, [chrono-tz](https://github.com/chronotope/chrono-tz) +and just released version 0.4.4 like two days ago. Meanwhile, [chrono-tz](https://github.com/chronotope/chrono-tz) appears to be dead in the water even though [there are people happy to help maintain it](https://github.com/chronotope/chrono-tz/issues/19). I know relatively little about it, but it appears that most of the release process is automated; keeping that up to date should be a no-brainer.