Develop release strategy about data-describe HOT 4 CLOSED

Here's the proposed release strategy, assuming we are releasing v0.1.0 and that we’ve done sufficient testing:

1. Create RELEASE.md file that includes the release notes for this version.
2. Update version numbers in setup.py
3. Create branch v0.1.0-release from master that includes the above changes
4. Turn this branch into protected branch
5. Create a release from this new branch via GitHub UI here
6. Build the package wheels and then use twine to publish the package on PyPI

Once it’s released, if there are any important bug fixes/patches, we can cherry-pick and backport the changes to v0.1.0-release or any past release branches. We follow Semantic Versioning for all releases.

from data-describe.

@terrytangyuan Do you recommend a particular method for single-sourcing the package version? I'll need to grab the current version to deploy documentation in #140

from data-describe.

Yes check out this example:

• https://github.com/scikit-learn-contrib/metric-learn/blob/master/metric_learn/_version.py
• https://github.com/scikit-learn-contrib/metric-learn/blob/master/setup.py#L42

from data-describe.

• Add to documentation

from data-describe.