mlderes / dstoolkit Goto Github PK

There is no auto-build for documentation. Consider using Sphinx.

As of now, the Makefile has some targets but it is unclear which targets are actually useful. This likely will have to be associated with a thoughtful approach to the build/release process.

The build / release process leaves room to be fixed. This is going to require a top-down approach to determine what the build and release cycle will look like. Here are a few scenarios that need to be considered

• Adding a new feature/fixing a bug. Does this mean a new branch, then what? Does every change require a pull request? If so, then how do we handle the pull requests, is this where the tag gets applied and the package gets built and released or should the build/test deployment /packages be built prior to the pull request, so that the pull request only needs to update the label and push the build to PyPI?