| 3 | | '''This page is currently being revised by mir@noris.de, please refrain from edits - 2007-01-13 23:45 UTC''' |
| | 3 | == Features Intended for 1.0 == |
| | 4 | |
| | 5 | The following features have either been decided to go into 1.0 or are under discussion. |
| | 6 | |
| | 7 | || '''Feature''' || '''Leader'''|| '''Changes API?''' || '''Implementation status''' || '''Tickets''' || |
| | 8 | || newforms || Adrian || Yes || on the way || || |
| | 9 | || serialization || Jacob || No || feature not clearly defined || #2930, #2843, #2650, #2553 || |
| | 10 | || authentication || Joseph || Yes || done || || |
| | 11 | || generic relations || Malcolm || Yes || not done || || |
| | 12 | || comments || Jacob || No || not started || || |
| | 13 | || oracle || ? || No || almost there || || |
| | 14 | || ms sql server || ? || No || ? || || |
| | 15 | || test fixtures || Russ || No || almost there || #2333 || |
| | 16 | || root views/url reversing|| ? || Yes || Not started || || |
| | 17 | || autoescape || Malcolm || No || almost there || || |
| | 18 | || model inheritance || Malcolm || Unclear || not started || || |
| | 19 | || windows installers|| ? || No || not started || || |
| | 20 | |
| | 21 | |
| | 22 | == Delayed Features == |
| | 23 | |
| | 24 | Left to those who decide ;-) |
| | 25 | |
| | 26 | == Comments about Specific Features == |
| | 27 | |
| | 28 | === Serialization === |
| | 29 | |
| | 30 | #2930 has not been decided and does not include a patch. |
| | 31 | |
| | 32 | #2843 is not changes the API only in a compatible way and there is no |
| | 33 | decision in the ticket. |
| | 34 | |
| | 35 | #2650 is a bug and not an enhancement, and it |
| | 36 | does not include a patch but complete files (but bug fixes should go in |
| | 37 | 1.0 anyway, if possible). |
| | 38 | |
| | 39 | #2553 proposes to make generic views respond |
| | 40 | in formats other than html, and it does not go into details nor does it |
| | 41 | include a patch. From the description I couldn't find out what it |
| | 42 | actually proposes, but it looks like a compatible change. |
| | 43 | |
| | 44 | === Comments === |
| | 45 | Jacob plans to rewrite them for newforms. I'd say this change |
| | 46 | actually belongs into the category 'newforms'. I'm not entirely |
| | 47 | convinced that it is necessary to rewrite the comments in 1.0, though. |
| | 48 | Other than the changes in admin, the comments system rewrite shouldn't |
| | 49 | directly influence the API of newforms. |
| | 50 | |
| | 51 | === Oracle === |
| | 52 | |
| | 53 | While it doesn't change APIs, having an oracle backend is great |
| | 54 | for the 1.0 release, even if it doesn't contribute to the #1 goal. And |
| | 55 | there is great impetus behind it. |
| | 56 | |
| | 57 | === Root View and URL Reversal === |
| | 58 | |
| | 59 | The root view proposal was blocked by the problem of url reversal. A few |
| | 60 | possible solutions have been brought up that had some disadvantages, and |
| | 61 | nobody of the core team has commented on this. |
| | 62 | |
| | 63 | === Autoescape === |
| | 64 | |
| | 65 | Autoescape only changed APIs if it was on by default. But I've followed |
| | 66 | the discussion very closely, and I'm sure that the main reaction of the |
| | 67 | community was strictly against this. autoescape is my own favorite pet, |
| | 68 | but when I apply my own criteria, it wouldn't be a candidate for 1.0. |
| | 69 | One could argue that it will deeply affect the way templates are written |
| | 70 | and that they are an important step to make django applications safe, |
| | 71 | but the consensus about it was not that strong. Or do we want to use it |
| | 72 | in the admin? |
| | 73 | |
| | 74 | |
| | 75 | |
| | 76 | = Obsolete = |
| | 77 | |
| | 78 | '''The following contents is out of date and will soon be moved into the sections above.''' |