floraachy
/
pytest2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Some more tweaks of how to release 

--HG--
branch : pytest-2.7
This commit is contained in:
Floris Bruynooghe 2015-05-01 00:27:04 +01:00
parent 652a353319
commit 129549fd5b
1 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
HOWTORELEASE.rst
View File

@ -15,7 +15,7 @@ How to release pytest (draft)
5. run from multiple machines: 5. run from multiple machines:
- ``devpi use https://devpi.net/USER/dev`` - ``devpi use https://devpi.net/USER/dev``
- ``devpi test pytest-VERSION`` - ``devpi test pytest==VERSION``
6. check that tests pass for relevant combinations with 6. check that tests pass for relevant combinations with
``devpi list pytest`` ``devpi list pytest``
@ -25,14 +25,15 @@ How to release pytest (draft)
which is ok (tox does not support skipping on which is ok (tox does not support skipping on
per-platform basis yet). per-platform basis yet).
7. XXX "regen docs" (not easy to do currently as it requires 7. Regenerate the docs using the toplevel makefile::
a development version of the regendoc tool from ronny) make docs
8. go to "doc/en" and upload docs with "make install" 8. Upload the docs using the toplevel makefile::
(the latter requires ssh-login permissions on pytest.org make upload-docs
because it uses rsync). Note that the "install" target of This requires ssh-login permission on pytest.org because it uses
doc/en/Makefile defines where the rsync goes to, typically rsync.
to the "latest" section of pytest.org. 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 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 is the name of pypi.python.org as configured in your