make pypi to upload to PYPI

[brunobord]

• add a makefile target to correctly upload to PYPI,
• allow using a different location (to use your own localshop / devpi mirror)

[Natim]

Would you guys use zest.releaser?

Here is the release flow we are using in most projects: http://kinto.readthedocs.io/en/stable/community.html#how-to-release

[brunobord]

zest.releaser is fine, and I'm using it (partially), but... its commit messages are dull (IMHO) and there's no way (apparently) to configure these messages - I personally dislike the "preparing release blah", which IS the release commit message

I'm using "prerelease" (and rewrite the commit message), and eventually "postrelease", but never "release + upload".
I prefer to do the upload myself, using the options I want for the PyPI/localshop I'm connected to (wheel or no wheel? binary dist or no binary dist? etc).

Just having a makefile target here would just be fine for me, kinda like a "remote control" I could eventually adapt to my specific needs when I'm not uploading on PYPI. But never-ever using the fullrelease subcommand.

[Natim]

It is because you do not have yet a review process for your releases (Reviewing the changelog for instance). When you do it makes a lot of sense: Kinto/kinto#663

[brunobord]

mmmm... using "prerelease" in a branch and "release" in master... interesting.

[brunobord]

done and released