Formalize a PyPi Release Process about maestrowf HOT 9 CLOSED

from maestrowf.

Would you be willing to make me a POC for the project in PYPI?

Same username "IanLee1521"

from maestrowf.

I've added you as a maintainer, did it go through?

from maestrowf.

@IanLee1521 -- Alright looks like you are a maintainer. Is there an accepted way of formalizing release. It looks like tagging, and using something like this article?

http://www.dougalmatthews.com/2016/Sep/01/automate-publishing-to-pypi-with-pbr-and-travis/

Do you know if that's the most current accepted way?

from maestrowf.

That's a bit fancier than what I've done... It tends to be (for most projects):

• Make a commit with the updated version string: git commit -am'Released version X.Y'
• Tag that commit: git tag -m 'Released version X.Y' X.Y
• Run build and release target, something like: python setup.py sdist bdist_wheel && twine upload dist/*

I tend to do something like have a Makefile target that does the right thing, at least for the building and pushing part (I prefer to do the first two steps manually).

from maestrowf.

Got it -- Might it be worthwhile exploring something fancier? It'd imagine that the CI integration will halt a release if it finds an issue.

from maestrowf.

I guess the question is "how often are you planning to do a release?" and what branches etc might you do that on?

Yes you could automate, but it might make sense to hold off until there is something to automate ;)

from maestrowf.

Also, I'm not positive how / if you could automate the pushing to PYPI... that might hold you up... (because you need to authenticate to the server).

from maestrowf.

Fair enough. I guess the better way to do this would be to just have a shell script (or maybe a make clause that takes a version?) that you give it the version and it automatically executes and then just lets you put in your password.

from maestrowf.