diff options
| author | Russell Keith-Magee <russell@keith-magee.com> | 2010-05-06 01:20:11 +0000 |
|---|---|---|
| committer | Russell Keith-Magee <russell@keith-magee.com> | 2010-05-06 01:20:11 +0000 |
| commit | 92983a3119d6af66b5b2099a0925092d520ee85a (patch) | |
| tree | 6f243dec69ae9e4cedfa0ebc3b6cdfd46f08ad82 /docs/faq | |
| parent | ee6d5521e94f8f94ad6e1e0f4eee94e2d4094350 (diff) | |
| download | django-92983a3119d6af66b5b2099a0925092d520ee85a.tar.gz | |
Fixed #12609 -- Updated FAQ on which version users should install. Thanks to shanx for the report.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@13109 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/faq')
| -rw-r--r-- | docs/faq/install.txt | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/faq/install.txt b/docs/faq/install.txt index 810247a1bc..492cc082f1 100644 --- a/docs/faq/install.txt +++ b/docs/faq/install.txt @@ -53,7 +53,7 @@ own version requirements. Over the next year or two Django will begin dropping support for older Python versions as part of a migration which will end with Django running on Python 3 -(see below for details). +(see below for details). All else being equal, we recommend that you use the latest 2.x release (currently Python 2.6). This will let you take advantage of the numerous @@ -92,11 +92,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. |