diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2006-03-16 02:58:25 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2006-03-16 02:58:25 +0000 |
| commit | a05e05a7f0e9c9c8f1e82e1a637994f14a1ef3b9 (patch) | |
| tree | 7bc010c02ea3c556f27d52c5eaff281b806ba51f /docs/faq.txt | |
| parent | b6fb43460b658726a6093701fa47012c3f202752 (diff) | |
Updated 1.0 date in docs/faq.txt
git-svn-id: http://code.djangoproject.com/svn/django/trunk@2523 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/faq.txt')
| -rw-r--r-- | docs/faq.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/faq.txt b/docs/faq.txt index 240cd166fd..977a3644fe 100644 --- a/docs/faq.txt +++ b/docs/faq.txt @@ -181,7 +181,7 @@ Short answer: When we're comfortable with Django's APIs, have added all features that we feel are necessary to earn a "1.0" status, and are ready to begin maintaining backwards compatibility. This should happen in a couple of months or so, although it's entirely possible that it could happen earlier. -That translates into February or March 2006. +That translates into summer 2006. Of course, you should note that `quite a few production sites`_ use Django in its current status. Don't let the lack of a 1.0 turn you off. |