summaryrefslogtreecommitdiff
path: root/docs/faq/install.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/faq/install.txt')
-rw-r--r--docs/faq/install.txt16
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/faq/install.txt b/docs/faq/install.txt
index 21dcaa9753..e0b08afc8b 100644
--- a/docs/faq/install.txt
+++ b/docs/faq/install.txt
@@ -87,11 +87,13 @@ See our `Django-friendly Web hosts`_ page.
.. _`Django-friendly Web hosts`: http://code.djangoproject.com/wiki/DjangoFriendlyWebHosts
-Should I use the official version or development version?
----------------------------------------------------------
+Should I use the stable version or development version?
+-------------------------------------------------------
-The Django developers improve Django every day and are pretty good about not
-checking in broken code. We use the development code (from the Subversion
-repository) directly on our servers, so we consider it stable. With that in
-mind, we recommend that you use the latest development code, because it
-generally contains more features and fewer bugs than the "official" releases.
+Generally, if you're using code in production, you should be using a
+stable release. The Django project publishes a full stable release
+every nine months or so, with bugfix updates in between. These stable
+releases contain the API that is covered by our backwards
+compatibility guarantees; if you write code against stable releases,
+you shouldn't have any problems upgrading when the next official
+version is released.