Changes between Version 41 and Version 42 of VersionOneFeatures


Ignore:
Timestamp:
01/13/2007 06:24:34 PM (8 years ago)
Author:
mir@…
Comment:

added summary of current mailing list activity

Legend:

Unmodified
Added
Removed
Modified
  • VersionOneFeatures

    v41 v42  
    11= Version 1.0 feature list =
    22
    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
     5The 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
     24Left 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
     33decision in the ticket.
     34
     35#2650 is a bug and not an enhancement, and it
     36does not include a patch but complete files (but bug fixes should go in
     371.0 anyway, if possible).
     38
     39#2553 proposes to make generic views respond
     40in formats other than html, and it does not go into details nor does it
     41include a patch. From the description I couldn't find out what it
     42actually proposes, but it looks like a compatible change.
     43
     44=== Comments ===
     45Jacob plans to rewrite them for newforms. I'd say this change
     46actually belongs into the category 'newforms'. I'm not entirely
     47convinced that it is necessary to rewrite the comments in 1.0, though.
     48Other than the changes in admin, the comments system rewrite shouldn't
     49directly influence the API of newforms.
     50
     51=== Oracle ===
     52
     53While it doesn't change APIs, having an oracle backend is great
     54for the 1.0 release, even if it doesn't contribute to the #1 goal. And
     55there is great impetus behind it.
     56
     57=== Root View and URL Reversal ===
     58
     59The root view proposal was blocked by the problem of url reversal. A few
     60possible solutions have been brought up that had some disadvantages, and
     61nobody of the core team has commented on this.
     62
     63=== Autoescape ===
     64
     65Autoescape only changed APIs if it was on by default. But I've followed
     66the discussion very closely, and I'm sure that the main reaction of the
     67community was strictly against this. autoescape is my own favorite pet,
     68but when I apply my own criteria, it wouldn't be a candidate for 1.0.
     69One could argue that it will deeply affect the way templates are written
     70and that they are an important step to make django applications safe,
     71but the consensus about it was not that strong. Or do we want to use it
     72in 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.'''
    479
    580'''Voting is now closed; see the "decision" column for the final call.'''  Trac milestones for all these features will be added shortly.
     81
    682
    783This is where we voted on the features we tossed around in [http://groups.google.com/group/django-developers/browse_thread/thread/5e629f571caec805/f2c0d8c85a2186b8#f2c0d8c85a2186b8 this django-developers thread]. Features that are done or nearly done have not been included.
Back to Top