<commit_before>
How to release pytest (draft)
--------------------------------------------

1. bump version numbers in setup.py and pytest/__init__.py

2. check and finalize CHANGELOG

3. write doc/en/announce/pytest-VERSION.txt and include
   it in doc/en/announce/index.txt

4. use devpi for uploading a release tarball to a staging area:
   - ``devpi use https://devpi.net/USER/dev`` 
   - ``devpi upload``

5. run from multiple machines:
   - ``devpi use https://devpi.net/USER/dev`` 
   - ``devpi test pytest-VERSION``

6. check that tests pass for relevant combinations with
   ``devpi list pytest`` 
   or look at failures with "devpi list -f pytest".
   There will be some failed environments like e.g. the py33-trial 
   or py27-pexpect tox environments on Win32 platforms
   which is ok (tox does not support skipping on
   per-platform basis yet).

7. 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. publish to pypi "devpi push pytest-2.6.2 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"

9. send release announcement to mailing lists:<commit_msg>mention XXX regendoc for release process<commit_after>
How to release pytest (draft)
--------------------------------------------

1. bump version numbers in setup.py and pytest/__init__.py

2. check and finalize CHANGELOG

3. write doc/en/announce/pytest-VERSION.txt and include
   it in doc/en/announce/index.txt

4. use devpi for uploading a release tarball to a staging area:
   - ``devpi use https://devpi.net/USER/dev`` 
   - ``devpi upload``

5. run from multiple machines:
   - ``devpi use https://devpi.net/USER/dev`` 
   - ``devpi test pytest-VERSION``

6. check that tests pass for relevant combinations with
   ``devpi list pytest`` 
   or look at failures with "devpi list -f pytest".
   There will be some failed environments like e.g. the py33-trial 
   or py27-pexpect tox environments on Win32 platforms
   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)

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.

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 
   ~/.pypirc file -- it's the same you would use with 
   "setup.py upload -r NAME"

10. send release announcement to mailing lists:
{'fraction_non_alphanumeric': 0.10890087660148348, 'fraction_numerical': 0.012811867835468645, 'mean_word_length': 2.8532467532467534, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6670112', 'n_tokens_mistral': 942, 'n_tokens_neox': 901, 'n_words': 395}