innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Updated 1.0 date in docs/faq.txt 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@2523 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Adrian Holovaty 2006-03-16 02:58:25 +00:00
parent b6fb43460b
commit a05e05a7f0
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/faq.txt
View File

@ -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 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 begin maintaining backwards compatibility. This should happen in a couple of
months or so, although it's entirely possible that it could happen earlier. 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 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. its current status. Don't let the lack of a 1.0 turn you off.