Code

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


Ignore:
Timestamp:
11/20/08 15:25:10 (5 years ago)
Author:
jacob
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Version1.1Roadmap

    v6 v7  
    1 = Django 1.1 roadmap and schedule = 
     1{{{ 
     2#!text/x-rst 
    23 
    3 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/. 
     4================== 
     5Django 1.1 Roadmap 
     6================== 
    47 
    5 == Django 1.1 Schedule == 
     8.. admonition:: DRAFT 
    69 
    7 Django 1.1 will be released the week of '''March 16th, 2009'''. 
     10    This is a **DRAFT** of the 1.1 roadmap which is currently being discussed 
     11    on `django-developers`_. The final roadmap will be posted in a few days. 
    812 
    9 The complete schedule follows. Note that dates are plus or minus a couple of days as needed. 
     13This document details the schedule and roadmap towards Django 1.1. All the 
     14details follow; here's the executive summary: 
    1015 
    11 || September 15, 2008   || Feature proposal phase begins (see [wiki:Version1.1Features Version1.1Features]) || 
    12 || November 7, 2008     || '''Deadline for feature proposals''' || 
    13 || November 10, 2008    || Posting of draft 1.1 feature list ||  
    14 || November 15, 2008    || Posting of the final 1.1 feature list posted; work phase begins. || 
    15 || 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. || 
    16 || January 20, 2009     || Django 1.1 alpha. 
    17 || February 15, 2009    || '''Feature freeze'''; only bug fixes will be allowed after this point. || 
    18 || February 20, 2009    || Django 1.1 beta. 
    19 || March 10, 2009       || '''String freeze''' 
    20 || March 12, 2009       || Django 1.1 rc 1. 
    21 || March 16-20, 2009    || '''Django 1.1 final''' 
     16    * Django 1.1 will be released `the week of March 16, 2009`__. 
     17     
     18    * As per our `official release process`_, Django 1.1 has a minimal set of 
     19      `must-have features`_. The big-ticket items on this list are model 
     20      validation and aggregation in the ORM. 
     21       
     22    * There's a larger list of `"maybe" features`_: if these features are done 
     23      before the 1.1 feature-freeze date (February 15), they'll be included  
     24      in Django 1.1. 
     25             
     26    * Those who want to help out should read the rest of this document, 
     27      especially `how you can help`_. 
     28       
     29    * You can follow the status of this process at the 
     30      :trac:`Version1.1Features` page. 
     31     
     32__ schedule_ 
     33.. _official release process: http://docs.djangoproject.com/en/dev/internals/release-process/ 
    2234 
    23 == Roadmap == 
     35What will be in Django 1.1? 
     36=========================== 
    2437 
    25 Features are currently being hashed out for 1.1. To propose a feature, make a 
    26 post on the django-developers mailing list, and add a link to your thread at [wiki:Version1.1Features Version1.1Features]. 
     38Over 60 features were proposed for Django 1.1. After discussion by the 
     39development community, these features were categorized "must have", "maybe", 
     40or "no" -- see our `official release process`_ for more information on how 
     41this works. 
     42 
     43Remember: see :trac:`Version1.1Features` for more details on each feature below; 
     44these are just summaries. 
     45 
     46Must-have features 
     47------------------ 
     48 
     49These are the features considered *critical* for the 1.1 release. 
     50 
     51    * [Admin-01] Bulk-edit on changelist pages. 
     52    * [Admin-02] Integrate django-batchadmin. 
     53    * [Admin-03] Make the admin use a URL resolver. 
     54    * [Admin-08] Make filters in admin changelists persistant. 
     55    * [Contrib-05] Message passing for anonymous users. 
     56    * [Contrib-12] Write-through cache session backend. 
     57    * [ORM-01] ORM aggregation. 
     58    * [ORM-03] Model validation. 
     59    * [ORM-06] Expression support in ``QuerySet.update()``. 
     60    * [ORM-14] Exclude fields in a ``SELECT`` (``QuerySet.defer()``) 
     61    * [Test-03] Run Django test cases inside a transaction (speed improvements). 
     62    * [View-01] Class-based generic views. 
     63 
     64"Maybe" features 
     65---------------- 
     66 
     67Again, these are features that *should* be in 1.1. In most cases, they're 
     68actively being worked on by members of the development community and will  
     69be checked in if finished in time. 
     70 
     71    * [Admin-05] ModelAdmin should allow for overriding of ``ForeignKey``/``ManyToMany`` options. 
     72    * [Admin-06] Read-only form fields. 
     73    * [Admin-07] Custom FilterSpecs. 
     74    * [Contrib-02] Improved customizability of ``django.contrib.comments``. 
     75    * [Contrib-03] Integration of comment-utils. 
     76    * [Contrib-06] Honor ``REMOTE_USER`` provided by the server 
     77    * [Contrib-07] Implement Atom Publishing Protocol. 
     78    * [Contrib-11] Signed cookies. 
     79    * [Form-01] Selectable HTML output for forms/fields. 
     80    * [ORM-15] Day-of-week filter for date/datetime Fields. 
     81    * [ORM-17] ``{% default %}`` clause for ``{% for %}`` loops. 
     82    * [ORM-19] Add support for database schemas. 
     83    * [Template-06] Better template tag loading. 
     84    * [Test-01] Follow redirect chains on the Test Client. 
     85    * [Test-02] Disable all e-mail sending for debugging. 
     86    * [View-03] Support for ``wsgi.file_wrapper`` for large files. 
     87     
     88Rejected/deferred features 
     89-------------------------- 
     90 
     91Astute readers will notice that only 28 features are listed above of the over 
     9260 that were proposed. The remaining features were rejected or deferred for a 
     93variety of reasons; see :trac:`Version1.1Features` for a complete list of 
     94these rejected features and reasons for rejection or deferral. 
     95 
     96Schedule 
     97======== 
     98 
     99Django 1.1 will be released the week of March 16th, 2009. 
     100 
     101The complete schedule follows. Note that dates are plus or minus a couple of 
     102days as needed: 
     103 
     104====================  ========================================================= 
     105January 15, 2009      "Major" feature freeze for 1.0; work phase ends, and any  
     106                      major incomplete features will be postponed. 
     107                       
     108January 20, 2009      Django 1.1 alpha. 
     109 
     110February 15, 2009     Feature freeze; only bug fixes will be allowed after  
     111                      this point. 
     112 
     113February 20, 2009     Django 1.1 beta. 
     114 
     115March 10, 2009        String freeze 
     116 
     117March 12, 2009        Django 1.1 rc 1. 
     118 
     119March 16-20, 2009     Django 1.1 final 
     120====================  ========================================================= 
     121 
     122We'll hold a series of :trac:`Sprints` to work on 1.1 starting in late 
     123December; stay tuned to the :trac:`Sprints` page and/or the 
     124`django-developers`_ mailing list for details. 
     125 
     126.. _django-developers: http://groups.google.com/group/django-developers 
     127 
     128Process 
     129======= 
     130 
     131Each feature on the list (both "must-have" and "maybe") will have a 
     132"lieutenant" (a term stolen from the Linux community) and a committer 
     133assigned. It's OK if this is the same person, but it's better if not: one 
     134committer can keep an eye and commit from patches from a number of trusted 
     135lieutenants. See :trac:`VersionOneFeatures` for the current list of 
     136lieutenants and committers. 
     137 
     138James Bennett, as the release manager, will be in charge of keeping the 
     139schedule. He'll keep track of who's working on what issues so that bug reports 
     140can be efficiently routed; he'll also nag, cajole and (if necessary) berate 
     141developers who are in danger of missing deadlines. 
     142 
     143How you can help 
     144---------------- 
     145 
     146The only way we'll meet this deadline is with a great deal of community effort. 
     147To that end, here's how you can help: 
     148 
     149    * Read the `guide to contributing to Django`__ and the `guide to Django's 
     150      release process`__. 
     151       
     152      These guides explains how our process works. where to ask questions, 
     153      etc. It'll save everyone time if we're all on the same page when it 
     154      comes to process. 
     155       
     156    * Work on features from the list above. 
     157 
     158      The joy of Open Source is that nobody gets to tell you what to do; you 
     159      can scratch whichever itch you like. However, if you work on items *not* 
     160      on the list of 1.1 features, you should expect that your patch won't get 
     161      checked in until after 1.1. 
     162     
     163      Get in touch with the lieutenant/committer for the feature you'd like 
     164      to work on and help out. Or just find open tickets and start submitting 
     165      patches! 
     166       
     167    * Attend a sprint (in person or in IRC). 
     168     
     169      We'll have four or five sprints between now and March. Lots of work gets 
     170      done at sprints, and there's usually someone around willing to help new 
     171      developers get started. 
     172 
     173    * Organize tickets. 
     174 
     175       * Feature tickets should go in the "1.1 alpha" or "1.1 beta" milestone.  
     176        
     177         Which one? Well, major changes must be made before the alpha, and 
     178         minor feature changes before the beta. So "major" feature additions 
     179         go in the alpha milestone, and minor additions in the beta one. If 
     180         you're not sure, then the feature is minor. 
     181          
     182         **Bugs** are **not** to be part of these milestone; any bug is a 
     183         candidate for fixing and should be left un-milestoned. The exception 
     184         is bugs in features added for 1.1; those should be in the "1.1" 
     185         milestone. 
     186 
     187    * Test the release snapshots (alphas, betas) against your code and report 
     188      bugs. 
     189       
     190      We need *lots* of testers if we're to have a bug-free release. Download 
     191      a snapshot or an SVN checkout and give it a try! 
     192       
     193__ http://docs.djangoproject.com/en/dev/internals/contributing/ 
     194__ http://docs.djangoproject.com/en/dev/internals/releases/ 
     195 
     196}}}