Move TODOs into issues

[tsalo]

Several items that need to be completed are currently in the file TODO.md, but they would be easier to track if a separate issue was opened for each item in the list and the file was removed.

For the automated testing, I would recommend aiming for 90% coverage and assigning the coverage issue to a future milestone (e.g., 2.0.0). I'm not sure how to quantify the documentation, but I guess it could be divided by submodule and tracked using a task list.

[bbfrederick]

Excellent idea. TODOs really need to be updated also. I'll do that in the next couple days - that will make the important ones trackable.

I like the idea of targeting 90% coverage as the trigger for a 2.0.0 release - the last week has really shown me the need for reliable automated testing - rapidtide2 was really broken for a few days, for kind of stupid reasons (fixed now). But if people that don't work in my building (so I can warn them) really are using it, I have to get that under control. I've been trying to be better about not pushing until I do tests...

[tsalo]

I opened an issue for test coverage (#13), but am not sure which of the remaining items in the TODO file are still pending.