<commit_before>===============
Release Process
===============

In order to allow for rapid, predictable releases, Setuptools uses a
mechanical technique for releases. The release script, ``release.py`` in the
repository, defines the details of the releases, and is executed by the
`jaraco.packaging <https://bitbucket.org/jaraco/jaraco.packaging>`_ release
module. The script does some checks (some interactive) and fully automates
the release process.

A Setuptools release manager must have maintainer access on PyPI to the
project and administrative access to the Bitbucket project.

To make a release, run the following from a Mercurial checkout at the
revision slated for release::

    python -m jaraco.packaging.release

Release Managers
----------------

<NAME> is the primary release manager. Additionally, the following
people have access to create releases:

- <NAME> (Ivoz)
<commit_msg>Update documentation on release frequency.<commit_after>===============
Release Process
===============

In order to allow for rapid, predictable releases, Setuptools uses a
mechanical technique for releases. The release script, ``release.py`` in the
repository, defines the details of the releases, and is executed by the
`jaraco.packaging <https://bitbucket.org/jaraco/jaraco.packaging>`_ release
module. The script does some checks (some interactive) and fully automates
the release process.

A Setuptools release manager must have maintainer access on PyPI to the
project and administrative access to the Bitbucket project.

To make a release, run the following from a Mercurial checkout at the
revision slated for release::

    python -m jaraco.packaging.release

Release Frequency
-----------------

Some have asked why Setuptools is released so frequently. Because Setuptools
uses a mechanical release process, it's very easy to make releases whenever the
code is stable (tests are passing). As a result, the philosophy is to release
early and often.

While some find the frequent releases somewhat surprising, they only empower
the user. Although releases are made frequently, users can choose the frequency
at which they use those releases. If instead Setuptools contributions were only
released in batches, the user would be constrained to only use Setuptools when
those official releases were made. With frequent releases, the user can govern
exactly how often he wishes to update.

Frequent releases also then obviate the need for dev or beta releases in most
cases. Because releases are made early and often, bugs are discovered and
corrected quickly, in many cases before other users have yet to encounter them.

Release Managers
----------------

<NAME> is the primary release manager. Additionally, the following
people have access to create releases:

- <NAME> (Ivoz)

{'fraction_non_alphanumeric': 0.08043087971274686, 'fraction_numerical': 0.0, 'mean_word_length': 4.527777777777778, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 2, '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': '2081816', 'n_tokens_mistral': 669, 'n_tokens_neox': 642, 'n_words': 377}