Release 1.0

[ysitu]

We follow the practice of NetworkX. We first release an RC and let it soak for some time. If there are no serious bugs reported, we release the finalized 1.0. Since networkx-metis is a new package, I suggest that we use a soak time of two weeks instead of one week in the case of NetworkX.

The specific steps:

1. Fix Change test_metis.py to test the exposed functions #26. This is a must. Only with this can we know whether the package does what it is purported to do. Fix AppVeyor CI #41 is optional. We can say that we initially do not officially support Windows.
2. Release RC. Create v1.0 branch and networkx-metis-1.0rc tag. Change setup.py in the branch to declare the version as 1.0rc and development status as beta. Build source distribution and upload to PyPI. (I suppose that bdist_wheel does not work when you have C extensions?)
3. Wait two weeks.
4. If no serious bugs are reported, Change setup.py in the branch to revert the version and development status changes. Create networkx-metis-1.0 tag. Build source distribution and upload to PyPI.

Please comment if there is anything missed.

[OrkoHunter]

I think now is the time to make the v1.0 branch.