Change Details

We run a custom git-fat package, which is in standard packages and deployed on every host. It's written in Python 2, which is EOL. Py3 support isn't completed upstream: https://github.com/jedbrown/git-fat/issues/92, so we could also collaborate with them if we want to continue to use git-fat.

~~We run a custom git-fat package, which is in standard packages and deployed on every host. It's written in Python 2, which is EOL. Py3 support isn't completed upstream: https://github.com/jedbrown/git-fat/issues/92, so we could also collaborate with them if we want to continue to use git-fat.~~ We need to stop using git-fat. It's antiquated, based on Python2, and there's better ways to do this. Mostly, this means using git-lfs, but it may also mean just not using large object storage in-tree at all, or just saying screw it the blobs aren't so big. Subtasks for each usage we have.

~~We run a custom git-fat package, which is in standard packages and deployed on every host. It's written in Python 2, which is EOL. Py3 support isn't completed upstream: https://github.com/jedbrown/git-fat/issues/92, so we could also collaborate with them if we want to continue to use git-fat.~~ We need to stop using git-fat. It's antiquated, based on Python2, and there's better ways to do this. Mostly, this means using git-lfs, but it may also mean just not using large object storage in-tree at all, or just saying screw it the blobs aren't so big. so we could also collaborate with them if we want to continue to use git-fatSubtasks for each usage we have.