diff --git a/HOWTORELEASE.rst b/HOWTORELEASE.rst index 2a21d4d0e..9f40b73f2 100644 --- a/HOWTORELEASE.rst +++ b/HOWTORELEASE.rst @@ -57,25 +57,25 @@ Note: this assumes you have already registered on pypi. cd doc/en make install # or "installall" if you have LaTeX installed for PDF - 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. + 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. - If you are making a minor release (e.g. 5.4), you also need to manually - create a symlink for "latest":: + If you are making a minor release (e.g. 5.4), you also need to manually + create a symlink for "latest":: - ssh pytest-dev@pytest.org - ln -s 5.4 latest + ssh pytest-dev@pytest.org + ln -s 5.4 latest - Browse to pytest.org to verify. + Browse to pytest.org to verify. 11. Publish to pypi:: devpi push pytest-VERSION pypi:NAME - where NAME is the name of pypi.python.org as configured in your ``~/.pypirc`` - file `for devpi `_. + where NAME is the name of pypi.python.org as configured in your ``~/.pypirc`` + file `for devpi `_. 12. Send release announcement to mailing lists: @@ -86,5 +86,5 @@ Note: this assumes you have already registered on pypi. 13. **after the release** Bump the version number in ``_pytest/__init__.py``, - to the next Minor release version (i.e. if you released ``pytest-2.8.0``, - set it to ``pytest-2.9.0.dev1``). + to the next Minor release version (i.e. if you released ``pytest-2.8.0``, + set it to ``pytest-2.9.0.dev1``).