From 129549fd5be59ccb5371da14e89995118c4a3a8c Mon Sep 17 00:00:00 2001 From: Floris Bruynooghe Date: Fri, 1 May 2015 00:27:04 +0100 Subject: [PATCH] Some more tweaks of how to release --HG-- branch : pytest-2.7 --- HOWTORELEASE.rst | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/HOWTORELEASE.rst b/HOWTORELEASE.rst index f4eed836b..77524079b 100644 --- a/HOWTORELEASE.rst +++ b/HOWTORELEASE.rst @@ -15,7 +15,7 @@ How to release pytest (draft) 5. run from multiple machines: - ``devpi use https://devpi.net/USER/dev`` - - ``devpi test pytest-VERSION`` + - ``devpi test pytest==VERSION`` 6. check that tests pass for relevant combinations with ``devpi list pytest`` @@ -25,14 +25,15 @@ How to release pytest (draft) which is ok (tox does not support skipping on per-platform basis yet). -7. XXX "regen docs" (not easy to do currently as it requires - a development version of the regendoc tool from ronny) +7. Regenerate the docs using the toplevel makefile:: + make docs -8. go to "doc/en" and upload docs with "make install" - (the latter requires ssh-login permissions on pytest.org - because it uses rsync). Note that the "install" target of - doc/en/Makefile defines where the rsync goes to, typically - to the "latest" section of pytest.org. +8. Upload the docs using the toplevel makefile:: + make upload-docs + This requires ssh-login permission on pytest.org because it uses + rsync. + Note that the "install" target of doc/en/Makefile defines where the + rsync goes to, typically to the "latest" section of pytest.org. 9. publish to pypi "devpi push pytest-2.6.2 pypi:NAME" where NAME is the name of pypi.python.org as configured in your