Make sure ProDy imports and passes all unit tests both Python 2 and Python 3, and using nose nosetests command:
$ cd ProDy
$ nosetests
$ nosetests3
See Testing ProDy for more on testing.
Update the version number in:
Also, commend + '-dev' out, so that documentation will build for a stable release.
Update the most recent changes and the latest release date in:
If there is a new incremental release, start a new file.
Make sure the following files are up-to-date.
If there is a new file format, that is a new extensions not captured in MANIFEST.in, it should be included.
If there is a new C extension, it should be listed in setup.py.
After checking these files, commit change and push them to GitHub.
Generate the source distributions:
$ cd ..
$ python setup.py sdist --formats=gztar,zip
Prepare and test Windows installers (see Making Windows Installers):
$ C:\Python26\python setup.py bdist_wininst
$ C:\Python27\python setup.py bdist_wininst
$ C:\Python32\python setup.py bdist_wininst
$ C:\Python33\python setup.py bdist_wininst
Alternatively, use bdist_wininst.bat to run these commands. When there is a newer Python major release, it should be added to this list.
Register new release to PyPI:
$ python setup.py register
Upload the new release files to the PyPI.
Commit final changes, if there are any:
$ cd ..
$ git commit -a
Tag the repository with the current version number:
$ git tag vX.Y
Rebase devel branch to master:
$ git checkout master
$ git rebase devel
Push the changes with the new tag:
$ git checkout master
$ git push --tags
$ git checkout devel
$ git push --tags
Finally, update the documentation on ProDy website. See Documenting ProDy.
Now that you made a release, you can go back to development. You may stat with append '-dev' to __release__ in prody/__init__.py.