Author: russellm Date: 2010-05-05 20:20:11 -0500 (Wed, 05 May 2010) New Revision: 13109
Modified: django/trunk/docs/faq/install.txt django/trunk/docs/internals/release-process.txt Log: Fixed #12609 -- Updated FAQ on which version users should install. Thanks to shanx for the report. Modified: django/trunk/docs/faq/install.txt =================================================================== --- django/trunk/docs/faq/install.txt 2010-05-06 01:19:45 UTC (rev 13108) +++ django/trunk/docs/faq/install.txt 2010-05-06 01:20:11 UTC (rev 13109) @@ -53,7 +53,7 @@ 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 @@ .. _`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. Modified: django/trunk/docs/internals/release-process.txt =================================================================== --- django/trunk/docs/internals/release-process.txt 2010-05-06 01:19:45 UTC (rev 13108) +++ django/trunk/docs/internals/release-process.txt 2010-05-06 01:20:11 UTC (rev 13109) @@ -47,7 +47,7 @@ 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: @@ -119,7 +119,7 @@ =============== 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 -- You received this message because you are subscribed to the Google Groups "Django updates" group. To post to this group, send email to django-upda...@googlegroups.com. To unsubscribe from this group, send email to django-updates+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-updates?hl=en.
