Version 1.0 Features

In addition to this list, the newforms-admin branch will need to be completed and merged prior to 1.0 (work is being done on this by a number of people). Discussion of this list of features and rationale for it is available in ​this thread on django-developers.

Unfinished Features

Feature	Leader	Changes API?	Implementation status	Tickets
django.templates __path__ hacking removal	?	Yes	not started	#6587
File storage refactoring	Marty	Yes	Complete, with docs and tests, awaiting verification from core devs	#5361
generic relations	Jacob/Malcolm	Yes	Code move is done (Malcolm), admin support (Jacob) not done. Needs newforms-admin merge first.	#4667
INSTALLED_APPS objects	?	Yes	not started	#3591
middleware ordering	?	No	not started	#730, #749
Model-level validation	Honza	?	in progress	#6845
newforms comments	Thejaswi Puthraya(GSOC 2008)	Yes	in progress	#1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189
newforms generic views	brosner	Unclear	Design decision needed. Contains docs and tests.	#3639
root views/url reversal	?	Yes	Not started	#2977
serialization	Jacob	No	feature not clearly defined	#2930, #2843, #2650, #2553
WSGI fixes	?	?	?	#285
Large streaming uploads	Mike Axiak	Yes	Complete, with docs and tests, awaiting verification from core devs	#2070

Completed Features

Feature	Leader	Changes API?	Implementation status	Tickets
authentication	Joseph	Yes	done
autoescape	Malcolm	Yes	done	#2359
DecimalField	Malcolm	Yes	done	#2365, #200, #2519, #3238, #3324
newforms	Adrian	Yes	done, but Django components need to migrate to it
oracle	?	No	done	#4140, #4186
test fixtures	Russ	No	done	#2333
Model inheritance	Malcolm	No	Available in trunk, post queryset-refactor merge, admin support coming in newforms-admin

Deferred/Post-1.0 Features

Feature	Leader	Changes API?	Implementation status	Tickets
ms sql server	?	No	no champion
windows installers	?	No	no champion
Comments refactor	Thejaswi Puthraya(GSOC 2008)	Yes	in progress	#1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189
ORM aggregation support	Nicolas Lara	No	Being developed as Google Summer of Code project

Comments about Specific Features

Serialization

#2930 has not been decided and does not include a patch.

#2843 is not changes the API only in a compatible way and there is no decision in the ticket.

#2650 is a bug and not an enhancement, and it does not include a patch but complete files (but bug fixes should go in 1.0 anyway, if possible).

#2553 proposes to make generic views respond in formats other than html, and it does not go into details nor does it include a patch. From the description it isn't clear what it actually proposes, but it looks like a compatible change.

Comments

Jacob plans to rewrite them for newforms. This change rather belongs into the category 'newforms'. Is it really necessary to rewrite the comments in 1.0? Other than the changes in admin, the comments system rewrite shouldn't directly influence the API of newforms. -- mir

Oracle

While it doesn't change APIs, having an Oracle backend is great for the 1.0 release, even if it doesn't contribute to the #1 goal. And there is great impetus behind it. Please see the Oracle Branch wiki page for technical details.

#4140 needs a design decision: should we warn or disallow database reserved words when used as column names?

#4186 is a significant limitation of Oracle and CLOB columns that can't be worked around, so we've at least documented the limitation clearly.

Root View and URL Reversal

The root view proposal was blocked by the problem of url reversal. A few possible solutions have been brought up that had some disadvantages, and nobody of the core team has commented on this.

Middleware ordering

We are not treating the middleware hierarchy as a stack, in the sense that if one piece of middleware short-circuits the response construction, we go right to the bottom of the pile before processing the request. We need to decide what behaviour we really want here and record it. Both the referenced tickets have good points in them and since this might slightly change request/response behaviour, it's a pre-1.0 decision if possible.

Comments refactor

The comments application needs to be, and will be, ported to use newforms prior to Django 1.0. However, Jacob has proposed developing a replacement for it which will be more generic and extensible; this does not need to happen before 1.0, and could simply be added as a new contrib app later on, leading to the eventual deprecation and phase-out of the original contrib.comments (which could in turn be maintained third-party by anyone who wants to keep it alive). To this end, a Google Summer of Code project is working on the refactor.