Update documentation on release frequency.

1 files changed, 19 insertions, 0 deletions

diff --git a/docs/releases.txt b/docs/releases.txt
index 66c0896f..4c8d6b8d 100644
--- a/docs/releases.txt
+++ b/docs/releases.txt
@@ -17,6 +17,25 @@ 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
 ----------------