Fixed #12609 -- Updated FAQ on which version users should install. Thanks to shanx for the report.

.. _`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.

Minor releases

--------------

Minor release (1.1, 1.2, etc.) will happen roughly every six months -- see

Minor release (1.1, 1.2, etc.) will happen roughly every nine months -- see

`release process`_, below for details.

.. _internal-release-deprecation-policy:

===============

Django uses a time-based release schedule, with minor (i.e. 1.1, 1.2, etc.)

releases every six months, or more, depending on features.

releases every nine months, or more, depending on features.

After each previous release (and after a suitable cooling-off period of a week

or two), the core development team will examine the landscape and announce a