Skip to content

Latest commit

 

History

History
15 lines (13 loc) · 1.04 KB

release.md

File metadata and controls

15 lines (13 loc) · 1.04 KB

Making a release

This is the internal checklist, so that @janschulz doesn't have to do another brown paper bag force-pushing the tags...

  • checkout git fetch origin && git checkout origin/master
  • run the tests (on windows): python tests.py -> everything ok?
  • increment the version in pypandoc/__init__.py, commit with git commit -m "pypandoc vx.x.x"
  • tag the version: git tag -a vx.x.x, write a nice version message summarizing new features
  • push directly to the repo (registered as orig_write in my setup): git push orig_write HEAD:master --tags
  • build the sdist file: python setup.py sdist
  • upload to PyPI: twine upload dist/pypandoc-<version>.zip
  • go to the package builder repo and increment the version information in recipes\pypandoc\meta.yml
  • commit with git commit -m "Build pypandoc vx.x.x"
  • git push -> builds arrive at PyPI and anaconda
  • celebrate :-)