Changes between Version 6 and Version 7 of Version1.1Roadmap

Timestamp:

Nov 20, 2008, 5:25:10 PM (16 years ago)

Author:

Jacob

Comment:

--

Version1.1Roadmap

@@ -1 @@
-= Django 1.1 roadmap and schedule =
+{{{
+#!text/x-rst
 
-This document details the schedule and (eventually) the roadmap for Django 1.1. For a general explanation of Django's release process and the phases of the release cycle, please refer to http://docs.djangoproject.com/en/dev/internals/release-process/.
+==================
+Django 1.1 Roadmap
+==================
 
-== Django 1.1 Schedule ==
+.. admonition:: DRAFT
 
-Django 1.1 will be released the week of '''March 16th, 2009'''.
+    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.
 
-The complete schedule follows. Note that dates are plus or minus a couple of days as needed.
+This document details the schedule and roadmap towards Django 1.1. All the
+details follow; here's the executive summary:
 
-|| September 15, 2008   || Feature proposal phase begins (see [wiki:Version1.1Features Version1.1Features]) ||
-|| November 7, 2008     || '''Deadline for feature proposals''' ||
-|| November 10, 2008    || Posting of draft 1.1 feature list || 
-|| November 15, 2008    || Posting of the final 1.1 feature list posted; work phase begins. ||
-|| January 15, 2009     || '''Major feature freeze''': work phase ends, and all open branches must be merged by this point. Any incomplete features will be postponed. ||
-|| January 20, 2009     || Django 1.1 alpha.
-|| February 15, 2009    || '''Feature freeze'''; only bug fixes will be allowed after this point. ||
-|| February 20, 2009    || Django 1.1 beta.
-|| March 10, 2009       || '''String freeze'''
-|| March 12, 2009       || Django 1.1 rc 1.
-|| March 16-20, 2009    || '''Django 1.1 final'''
+    * Django 1.1 will be released `the week of March 16, 2009`__.
+    
+    * As per our `official release process`_, Django 1.1 has a minimal set of
+      `must-have features`_. The big-ticket items on this list are model
+      validation and aggregation in the ORM.
+      
+    * There's a larger list of `"maybe" features`_: if these features are done
+      before the 1.1 feature-freeze date (February 15), they'll be included 
+      in Django 1.1.
+            
+    * Those who want to help out should read the rest of this document,
+      especially `how you can help`_.
+      
+    * You can follow the status of this process at the
+      :trac:`Version1.1Features` page.
+    
+__ schedule_
+.. _official release process: http://docs.djangoproject.com/en/dev/internals/release-process/
 
-== Roadmap ==
+What will be in Django 1.1?
+===========================
 
-Features are currently being hashed out for 1.1. To propose a feature, make a
-post on the django-developers mailing list, and add a link to your thread at [wiki:Version1.1Features Version1.1Features].
+Over 60 features were proposed for Django 1.1. After discussion by the
+development community, these features were categorized "must have", "maybe",
+or "no" -- see our `official release process`_ for more information on how
+this works.
+
+Remember: see :trac:`Version1.1Features` for more details on each feature below;
+these are just summaries.
+
+Must-have features
+------------------
+
+These are the features considered *critical* for the 1.1 release.
+
+    * [Admin-01] Bulk-edit on changelist pages.
+    * [Admin-02] Integrate django-batchadmin.
+    * [Admin-03] Make the admin use a URL resolver.
+    * [Admin-08] Make filters in admin changelists persistant.
+    * [Contrib-05] Message passing for anonymous users.
+    * [Contrib-12] Write-through cache session backend.
+    * [ORM-01] ORM aggregation.
+    * [ORM-03] Model validation.
+    * [ORM-06] Expression support in ``QuerySet.update()``.
+    * [ORM-14] Exclude fields in a ``SELECT`` (``QuerySet.defer()``)
+    * [Test-03] Run Django test cases inside a transaction (speed improvements).
+    * [View-01] Class-based generic views.
+
+"Maybe" features
+----------------
+
+Again, these are features that *should* be in 1.1. In most cases, they're
+actively being worked on by members of the development community and will 
+be checked in if finished in time.
+
+    * [Admin-05] ModelAdmin should allow for overriding of ``ForeignKey``/``ManyToMany`` options.
+    * [Admin-06] Read-only form fields.
+    * [Admin-07] Custom FilterSpecs.
+    * [Contrib-02] Improved customizability of ``django.contrib.comments``.
+    * [Contrib-03] Integration of comment-utils.
+    * [Contrib-06] Honor ``REMOTE_USER`` provided by the server
+    * [Contrib-07] Implement Atom Publishing Protocol.
+    * [Contrib-11] Signed cookies.
+    * [Form-01] Selectable HTML output for forms/fields.
+    * [ORM-15] Day-of-week filter for date/datetime Fields.
+    * [ORM-17] ``{% default %}`` clause for ``{% for %}`` loops.
+    * [ORM-19] Add support for database schemas.
+    * [Template-06] Better template tag loading.
+    * [Test-01] Follow redirect chains on the Test Client.
+    * [Test-02] Disable all e-mail sending for debugging.
+    * [View-03] Support for ``wsgi.file_wrapper`` for large files.
+    
+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.
+
+Schedule
+========
+
+Django 1.1 will be released the week of March 16th, 2009.
+
+The complete schedule follows. Note that dates are plus or minus a couple of
+days as needed:
+
+====================  =========================================================
+January 15, 2009      "Major" feature freeze for 1.0; work phase ends, and any 
+                      major incomplete features will be postponed.
+                      
+January 20, 2009      Django 1.1 alpha.
+
+February 15, 2009     Feature freeze; only bug fixes will be allowed after 
+                      this point.
+
+February 20, 2009     Django 1.1 beta.
+
+March 10, 2009        String freeze
+
+March 12, 2009        Django 1.1 rc 1.
+
+March 16-20, 2009     Django 1.1 final
+====================  =========================================================
+
+We'll hold a series of :trac:`Sprints` to work on 1.1 starting in late
+December; stay tuned to the :trac:`Sprints` page and/or the
+`django-developers`_ mailing list for details.
+
+.. _django-developers: http://groups.google.com/group/django-developers
+
+Process
+=======
+
+Each feature on the list (both "must-have" and "maybe") will have a
+"lieutenant" (a term stolen from the Linux community) and a committer
+assigned. It's OK if this is the same person, but it's better if not: one
+committer can keep an eye and commit from patches from a number of trusted
+lieutenants. See :trac:`VersionOneFeatures` for the current list of
+lieutenants and committers.
+
+James Bennett, as the release manager, will be in charge of keeping the
+schedule. He'll keep track of who's working on what issues so that bug reports
+can be efficiently routed; he'll also nag, cajole and (if necessary) berate
+developers who are in danger of missing deadlines.
+
+How you can help
+----------------
+
+The only way we'll meet this deadline is with a great deal of community effort.
+To that end, here's how you can help:
+
+    * Read the `guide to contributing to Django`__ and the `guide to Django's
+      release process`__.
+      
+      These guides explains how our process works. where to ask questions,
+      etc. It'll save everyone time if we're all on the same page when it
+      comes to process.
+      
+    * Work on features from the list above.
+
+      The joy of Open Source is that nobody gets to tell you what to do; you
+      can scratch whichever itch you like. However, if you work on items *not*
+      on the list of 1.1 features, you should expect that your patch won't get
+      checked in until after 1.1.
+    
+      Get in touch with the lieutenant/committer for the feature you'd like
+      to work on and help out. Or just find open tickets and start submitting
+      patches!
+      
+    * Attend a sprint (in person or in IRC).
+    
+      We'll have four or five sprints between now and March. Lots of work gets
+      done at sprints, and there's usually someone around willing to help new
+      developers get started.
+
+    * Organize tickets.
+
+       * Feature tickets should go in the "1.1 alpha" or "1.1 beta" milestone. 
+       
+         Which one? Well, major changes must be made before the alpha, and
+         minor feature changes before the beta. So "major" feature additions
+         go in the alpha milestone, and minor additions in the beta one. If
+         you're not sure, then the feature is minor.
+         
+         **Bugs** are **not** to be part of these milestone; any bug is a
+         candidate for fixing and should be left un-milestoned. The exception
+         is bugs in features added for 1.1; those should be in the "1.1"
+         milestone.
+
+    * Test the release snapshots (alphas, betas) against your code and report
+      bugs.
+      
+      We need *lots* of testers if we're to have a bug-free release. Download
+      a snapshot or an SVN checkout and give it a try!
+      
+__ http://docs.djangoproject.com/en/dev/internals/contributing/
+__ http://docs.djangoproject.com/en/dev/internals/releases/
+
+}}}