Clean up on aisle 2.0.0...

[JohnKallies]

Ideally, we would have tested release automation that runs 100% correctly. But we did the 2.0.0 release manually to meet a timeline. The act of creating tags for a release and pushing to develop, then master, then a release branch... something got messed up.

tldr; The previous develop branch got renamed and replaced with a new develop branch, and there may have been a force push somewhere along the way. For anyone affected by these shenanigans, you should be able to rebase any feature work in progress onto the current develop branch, following something like this...

git checkout develop
git fetch
# ensure you don't have work in progress on your local develop
git reset --hard origin/develop
git checkout my-feature-branch
git pull --rebase origin develop

This isn't the right way to manage a release. We will be able to prioritize release automation in the near future. If this goof affected you, we'll do better next time, and we appreciate your patience as we get there.