SILENT KILLER Tool

Name	Type	Size	Last Modified
asl.txt	File	11358 bytes	November 13 2023 21:11:31.
developer-guide.txt	File	4118 bytes	August 28 2017 13:45:10.
development.txt	File	1474 bytes	August 28 2017 13:45:10.
easy_install.txt	File	75545 bytes	August 28 2017 13:45:10.
formats.txt	File	31242 bytes	August 28 2017 13:45:10.
history.txt	File	1887 bytes	August 28 2017 13:45:10.
index.txt	File	537 bytes	August 28 2017 13:45:10.
pkg_resources.txt	File	94391 bytes	August 28 2017 13:45:10.
psfl.txt	File	12767 bytes	November 13 2023 21:11:31.
python3.txt	File	3970 bytes	August 28 2017 13:45:10.
releases.txt	File	2114 bytes	August 28 2017 13:45:10.
requirements.txt	File	61 bytes	August 28 2017 13:45:10.
roadmap.txt	File	167 bytes	August 28 2017 13:45:10.
setuptools.txt	File	126650 bytes	August 28 2017 13:45:10.
zpl.txt	File	2070 bytes	November 13 2023 21:11:31.

===============
Release Process
===============

In order to allow for rapid, predictable releases, Setuptools uses a
mechanical technique for releases, enacted by Travis following a
successful build of a tagged release per
`PyPI deployment <https://docs.travis-ci.com/user/deployment/pypi>`_.

Prior to cutting a release, please check that the CHANGES.rst reflects
the summary of changes since the last release.
Ideally, these changelog entries would have been added
along with the changes, but it's always good to check.
Think about it from the
perspective of a user not involved with the development--what would
that person want to know about what has changed--or from the
perspective of your future self wanting to know when a particular
change landed.

To cut a release, install and run ``bump2version {part}`` where ``part``
is major, minor, or patch based on the scope of the changes in the
release. Then, push the commits to the master branch. If tests pass,
the release will be uploaded to PyPI (from the Python 3.6 tests).

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
----------------

Additionally, anyone with push access to the master branch has access to cut
releases.

SILENT KILLERPanel

Files and Folders in: //opt/alt/python27/share//doc/alt-python27-setuptools

Reading File: //opt/alt/python27/share//doc/alt-python27-setuptools/releases.txt