From 760ed9987a2fe6c990cba8e61e328e49ae64bf4e Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Thu, 6 May 2010 01:26:39 +0000 Subject: [1.1.X] Fixed #12609 -- Updated FAQ on which version users should install. Thanks to shanx for the report. Backport of r13109 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@13112 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/faq/install.txt | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) (limited to 'docs/faq') 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? ---------------------------------------------------------- - -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. +Should I use the stable version or development version? +------------------------------------------------------- + +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. -- cgit v1.3