summaryrefslogtreecommitdiff
path: root/docs/faq.txt
diff options
context:
space:
mode:
authorJason Pellerin <jpellerin@gmail.com>2006-12-04 19:58:49 +0000
committerJason Pellerin <jpellerin@gmail.com>2006-12-04 19:58:49 +0000
commit040f2272e0aec724a36e7abda445b61ee065a8f1 (patch)
tree8ae714be4e513663470eaf1d3d8026a92a5cd2f8 /docs/faq.txt
parent2a58209ff2b7c47245c9d12985ac7581e97988d1 (diff)
[multi-db] Merged trunk to 3950. Some tests still failing.
git-svn-id: http://code.djangoproject.com/svn/django/branches/multiple-db-support@4155 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs/faq.txt')
-rw-r--r--docs/faq.txt4
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/faq.txt b/docs/faq.txt
index c7f92d3580..eaccc6be43 100644
--- a/docs/faq.txt
+++ b/docs/faq.txt
@@ -227,9 +227,7 @@ When will you release Django 1.0?
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 summer 2006.
+begin maintaining backwards compatibility.
The merging of Django's `magic-removal branch`_ went a long way toward Django
1.0.