[Pytest-commit] commit/pytest: flub: Add how to upload a wheel and tag the release

[commits-noreply at bitbucket.org]

1 new commit in pytest:

https://bitbucket.org/pytest-dev/pytest/commits/b3273466be77/
Changeset:   b3273466be77
Branch:      pytest-2.7
User:        flub
Date:        2015-05-19 08:32:21+00:00
Summary:     Add how to upload a wheel and tag the release
Affected #:  1 file

diff -r a62cf0013b3546d38f1a6295d04413d9fb37f5f3 -r b3273466be77f4827e46d37b24bd4c974a0b8edf HOWTORELEASE.rst
--- a/HOWTORELEASE.rst
+++ b/HOWTORELEASE.rst
@@ -11,7 +11,7 @@
 
 4. use devpi for uploading a release tarball to a staging area:
    - ``devpi use https://devpi.net/USER/dev`` 
-   - ``devpi upload``
+   - ``devpi upload --formats sdist,bdist_wheel``
 
 5. run from multiple machines:
    - ``devpi use https://devpi.net/USER/dev`` 
@@ -35,7 +35,10 @@
       cd docs/en
       make html
 
-9. Upload the docs using docs/en/Makefile::
+9. Tag the release::
+      hg tag VERSION
+
+10. Upload the docs using docs/en/Makefile::
       cd docs/en
       make install  # or "installall" if you have LaTeX installed
    This requires ssh-login permission on pytest.org because it uses
@@ -43,12 +46,12 @@
    Note that the "install" target of doc/en/Makefile defines where the
    rsync goes to, typically to the "latest" section of pytest.org.
 
-10. publish to pypi "devpi push pytest-2.6.2 pypi:NAME" where NAME 
+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 -- it's the same you would use with 
    "setup.py upload -r NAME"
 
-11. send release announcement to mailing lists:
+12. send release announcement to mailing lists:
 
    pytest-dev
    testing-in-python

Repository URL: https://bitbucket.org/pytest-dev/pytest/

--

This is a commit notification from bitbucket.org. You are receiving
this because you have the service enabled, addressing the recipient of
this email.