alamb commented on issue #9183:
URL: https://github.com/apache/arrow-rs/issues/9183#issuecomment-6950137481

   Yeah I think it is time. I think the first ting we need to do is figure out 
where chrono appears in the public API (it is in many places) and put a 
compatibility layer in place (e.g. a `chrono` feature that enables all the old 
APIs, ut deprecate them)
   
   Then we can freely replace the internals to use jiff
   
   That should minimize the disruption to downstream users and give them time 
to adjust


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to