Since we are trying to be verbose in these issues and PRs, we should really have a document like Cyclus's CHANGELOG.rst to keep track of the evolution of features and parts of this code.
This issue can be closed by a PR with a changelog file that outlines the progress up to this point.
Since we are trying to be verbose in these issues and PRs, we should really have a document like Cyclus's CHANGELOG.rst to keep track of the evolution of features and parts of this code.
This issue can be closed by a PR with a changelog file that outlines the progress up to this point.