| 7 | | || '''Feature''' || '''Leader'''|| '''Changes API?''' || '''Implementation status''' || '''Tickets''' || |
| 8 | | || `django.templates` `__path__` hacking removal || ? || Yes || not started || #6587 || |
| 9 | | || File storage refactoring || Marty || Yes || Complete, with docs and tests, awaiting verification from core devs. Depends on streaming-upload refactor below || #5361 || |
| 10 | | || generic relations || Jacob/Malcolm || Yes || Code move is done (Malcolm), admin support (Jacob) not done. Needs newforms-admin merge first. || #4667 || |
| 11 | | || `INSTALLED_APPS` objects || ? || Yes || not started || #3591 || |
| 12 | | || [#Middlewareordering middleware ordering] || ? || No || not started || #730, #749 || |
| 13 | | || Model-level validation || Honza || ? || in progress || #6845 || |
| 14 | | || newforms comments || Thejaswi Puthraya(GSOC 2008) || Yes || in progress || #1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189 || |
| 15 | | || newforms generic views || brosner || Unclear || Design decision needed. Contains docs and tests. || #3639 || |
| 16 | | || [#RootViewandURLReversal root views/url reversal]|| ? || Yes || Not started || #2977 || |
| 17 | | || [#Serialization serialization] || Jacob || No || feature not clearly defined || #2930, #2843, #2650, #2553 || |
| 18 | | || WSGI fixes || Needs someone to step up || No || not started || #285 || |
| 19 | | || Large streaming uploads || Mike Axiak || Yes || Complete, with docs and tests, awaiting verification from core devs || #2070 || |
| 20 | | || Dispatcher refactor || Jacob/Jeremy || Maybe || In progress || |
| | 7 | === Must-have features === |
| 24 | | || '''Feature''' || '''Leader'''|| '''Changes API?''' || '''Implementation status''' || '''Tickets''' || |
| 25 | | || authentication || Joseph || Yes || done || || |
| 26 | | || [#Autoescape autoescape] || Malcolm || Yes || done || #2359 || |
| 27 | | || [#DecimalField DecimalField] || Malcolm || Yes || done || #2365, #200, #2519, #3238, #3324 || |
| 28 | | || newforms || Adrian || Yes || done, but Django components need to migrate to it || || |
| 29 | | || [#Oracle oracle] || ? || No || done || #4140, #4186 || |
| 30 | | || test fixtures || Russ || No || done || #2333 || |
| 31 | | || Model inheritance || Malcolm || No || Available in trunk, post queryset-refactor merge, admin support coming in newforms-admin || || |
| | 14 | === "Maybe" features === |
| 33 | | |
| 34 | | == Deferred/Post-1.0 Features == |
| 35 | | |
| 36 | | || '''Feature''' || '''Leader'''|| '''Changes API?''' || '''Implementation status''' || '''Tickets''' || |
| 37 | | || ms sql server || ? || No || no champion || || |
| 38 | | || windows installers || ? || No || no champion || || |
| 39 | | || [#Commentsrefactor Comments refactor] || Thejaswi Puthraya(GSOC 2008) || Yes || in progress || #1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189 || |
| 40 | | || ORM aggregation support || Nicolas Lara || No || Being developed as Google Summer of Code project || || |
| | 16 | || '''Feature''' || '''Lieutenant''' || '''Committer'''' || '''Status''' || '''Tickets''' || |
| | 17 | || Signal performance improvements || Jeremy Dunck || JKM || needs feedback || #6814 || |
| | 18 | || Large file uploads || Mike Axiak || JKM || ready for checkin || #2070 || |
| | 19 | || INSTALLED_APPS refactoring || ''???'' || ''???'' || not started || #3591 || |
| | 20 | || File storage refactoring || Marty Alchin || JKM || depends on #2070 || #5361 || |
| | 21 | || Model-level validation || Honza Král || JKM || started || #6845 || |
| | 22 | || GenericForeignKey support in nfa || ''???'' || ''???'' || not started || #4667 || |
| | 23 | || GeoDjango || Justin Bronn || Justin Bronn || ''???'' || || |
| | 24 | || Many-to-many intermediates || Eric Florenzano || Russ || nearly done; has admin issues || #6095 || |
| | 25 | || Fix alternative Python VM bugs. || ''???'' || JKM || ''???'' || || |
| | 26 | || De-cruftify template tag loading || ''???'' || ''???'' || ''???'' || #6587, ... || |
| | 27 | || Middleware ordering || ''???'' || JKM || ''???'' || #730, #749 || |
| | 28 | || Self-referencing fields in queries || ''???'' || Russ || ''???'' || #7210 |
| | 29 | || Finish documentation refactoring || ''???'' || JKM || needs work || || |
| | 30 | || [#Commentsrefactor Comments refactor] || Thejaswi Puthraya (GSOC 2008) || ''???'' || in progress || #1829, #1853, #2134, #2177, #2228, #3091, #3546, #4189 || |
| 46 | | #2930 has not been decided and does not include a patch. |
| 47 | | |
| 48 | | #2843 is not changes the API only in a compatible way and there is no |
| 49 | | decision in the ticket. |
| 50 | | |
| 51 | | #2650 is a bug and not an enhancement, and it |
| 52 | | does not include a patch but complete files (but bug fixes should go in |
| 53 | | 1.0 anyway, if possible). |
| 54 | | |
| 55 | | #2553 proposes to make generic views respond |
| 56 | | in formats other than html, and it does not go into details nor does it |
| 57 | | include a patch. From the description it isn't clear what it |
| 58 | | actually proposes, but it looks like a compatible change. |
| 59 | | |
| 60 | | === Comments === |
| 61 | | Jacob plans to rewrite them for newforms. This change rather |
| 62 | | belongs into the category 'newforms'. Is it really necessary to rewrite the comments in 1.0? |
| 63 | | Other than the changes in admin, the comments system rewrite shouldn't |
| 64 | | directly influence the API of newforms. -- mir |
| 65 | | |
| 66 | | === Oracle === |
| 67 | | |
| 68 | | While it doesn't change APIs, having an Oracle backend is great |
| 69 | | for the 1.0 release, even if it doesn't contribute to the #1 goal. And |
| 70 | | there is great impetus behind it. Please see the [wiki:OracleBranch Oracle Branch] wiki page for technical details. |
| 71 | | |
| 72 | | #4140 needs a design decision: should we warn or disallow database reserved words when used as column names? |
| 73 | | |
| 74 | | #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. |
| 75 | | |
| 76 | | === Root View and URL Reversal === |
| 77 | | |
| 78 | | The root view proposal was blocked by the problem of url reversal. A few |
| 79 | | possible solutions have been brought up that had some disadvantages, and |
| 80 | | nobody of the core team has commented on this. |
| | 36 | See VersionOneRoadmap for details. |
| 84 | | 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. |
| 85 | | |
| 86 | | === Comments refactor === |
| 87 | | |
| 88 | | 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. |
| | 40 | We are not treating the middleware hierarchy as a stack, in the sense that if |
| | 41 | one piece of middleware short-circuits the response construction, we go right to |
| | 42 | the bottom of the pile before processing the request. We need to decide what |
| | 43 | behaviour we really want here and record it. Both the referenced tickets have |
| | 44 | good points in them and since this might slightly change request/response |
| | 45 | behaviour, it's a pre-1.0 decision if possible. |