> Git is distributed, so when GitHub goes down, every developer has a backup of entire history. However, issues are lost forever. Python does not use "issues" f

> Git is distributed, so when GitHub goes down, every developer has a backup of entire history. However, issues are lost forever. Python does not use "issues" feature for good. um, no? PEP-512 ( https://www.python.org/dev/peps/pep-0512/ https://www.python.org/dev/peps/pep-0512/ ) is pretty clear about it: "The code review history does not have the same implicit backup mechanism as the repository itself. That means a daily backup of code review history should be done so that it is not lost in case of any issues with GitHub."