diff options
| author | Akash Kumar Sen <71623442+Akash-Kumar-Sen@users.noreply.github.com> | 2023-05-08 12:04:23 +0530 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-05-08 08:34:23 +0200 |
| commit | aaf8c76c567e8311f4a85cf74c82fc3d70cc6f12 (patch) | |
| tree | bd6ef143000e423c65276aeca3193d8f373ec18e /docs | |
| parent | 12ec80726f33e8dbd80de3cecf48d76ac4c0aa89 (diff) | |
| download | django-aaf8c76c567e8311f4a85cf74c82fc3d70cc6f12.tar.gz | |
Fixed #34545 -- Corrected the number of months in installation FAQ.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/faq/install.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq/install.txt b/docs/faq/install.txt index 402f7d7497..621b314734 100644 --- a/docs/faq/install.txt +++ b/docs/faq/install.txt @@ -83,7 +83,7 @@ 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 +every eight 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 |