Changes between Version 8 and Version 9 of Version1.1Roadmap

Timestamp:

Nov 20, 2008, 7:02:27 PM (17 years ago)

Author:

Jacob

Comment:

--

Version1.1Roadmap

@@ -6 +6 @@
 ==================
 
-**This is a DRAFT of the 1.1 roadmap which is currently being discussed on django-developers. The final roadmap will be posted in a few days.**
+**This is a DRAFT of the 1.1 roadmap which is currently being discussed on
+django-developers. The final roadmap will be posted in a few days.**
 
 This document details the schedule and roadmap towards Django 1.1. All the
@@ -65 +66 @@
 actively being worked on by members of the development community and will 
 be checked in if finished in time.
+
+The following features have committers who'll take responsibility for getting
+the feature in; as such they can be considered a sort of "first-priority" of
+among the "maybe" features:
 
     * [Admin-05] ModelAdmin should allow for overriding of ``ForeignKey``/``ManyToMany`` options.
@@ -83 +88 @@
     * [View-03] Support for ``wsgi.file_wrapper`` for large files.
     
+The following features were reviewed highly and are generally accepted as
+"wanted", but currently are lacking a "champion" to see the feature done. This
+means these features are likely to be included in 1.1 if finished, but are
+a sort of "second-tier":
+
+    * [Contrib-01] Session-based form wizard.
+    * [Form-02] ``django.forms.SafeForm`` - forms with built-in CSRF protection.
+    * [ORM-09] ``Manager.update_or_create()`` and ``Model.update()``.
+    * [ORM-10] ``QuerySet.select_for_update()`` method.
+    * [ORM-11] ``QuerySet.cache()`` method.
+    * [ORM-12] Allow the use of ``property()`` in fields.
+    * [ORM-13] Support for ``DISTINCT ON`` queries with ``QuerySet.distinct()``.
+    * [ORM-16] Native autocommit option for Postgresql backend.
+    * [ORM-18] Add signals to many-to-many objects.
+    * [Template-01] Extend inclusion tag syntax to allow custom templates.
+    * [Template-04] Clean-up of ``django.template`` internals.
+    * [Template-05] Namespace support for template libraries.
+
+Special cases
+-------------
+
+As is to be expected, a few features don't fit so easily into any of the hard
+categories:
+
+    * [ORM-05] Sharing of ``selected_related()`` data in memory, and/or an
+      ORM identity map.
+      
+      The scope of this feature is a bit nebulous, but it's under discussion
+      on `django-developers`_. If consensus is reached and the feature can
+      be implemented in time, it'll get into 1.1.
+      
+    * [Form-01] Selectable HTML output for forms/fields.
+    
+      This feature is similarly not fully-scoped, though this one has a
+      reference implementation so it's further along. However,, there's a fair
+      bit of controversy about the particular proposed implementation. Again,
+      consensus is the issue here; discussion is ongoing.
+      
+    * [View-02] Add ``RequestContext`` by default in ``render_to_response``.
+    
+      This proposal is strongly controversial, with multiple +1 and -1 votes.
+      As such, consensus seems unlikely; a middle-ground approach will need be
+      found, which likely pushes this out of scope for 1.1.
+
 Rejected/deferred features
 --------------------------
 
-Astute readers will notice that only 28 features are listed above of the over
-60 that were proposed. The remaining features were rejected or deferred for a
-variety of reasons; see :trac:`Version1.1Features` for a complete list of
-these rejected features and reasons for rejection or deferral.
+The remaining proposed features were rejected or deferred for a variety of
+reasons; see :trac:`Version1.1Features` for a complete list of these rejected
+features and reasons for rejection or deferral.
 
 Schedule
@@ -152 +200 @@
       
     * Work on features from the list above.
+
 
       The joy of Open Source is that nobody gets to tell you what to do; you