melutovich

@ncalexan Did you ever discuss this with the mercurial developers/existing extension writers?

@ncalexan @Wilfred Besides the above comments by Mekk there is a related mercurial list thread https://lists.mercurial-scm.org/pipermail/mercurial/2023-September/106330.html

@Wilfred @ncalexan Where are we holding with this? (As you can guess by my recent pings around here, I'm looking at monky; for a new server, dvc does not work...

@IvyBaumgarb @PeteLambert89 I made a post on https://gitter.im/MicroPyramid/Django-CRM on Jan 5th and there has been no response, that was discouraging for me. I believe the developers are active but much...

@TamaMcGlinn You could see if the pull request might be better received at https://github.com/zigdon/wemux

What became of this?

@ehuelsmann I will assume from you that Workflow's usage of DateTime is actually hitting that serious performance impact. Perhaps the Workflow system could reference a new Workflow::DateTime which would be...

@ehuelsmann I've have not taken a serious look at the code so I also have to assume that your statement earlier of "Our purpose isn't to calculate with dates, time...

> However, they do not test backward compatibility of data that was stored by version 1.x with version 2.x (which would be switched to DateTime::Tiny). I did not understand what...