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


Ignore:
Timestamp:
Jan 16, 2015, 5:48:17 PM (10 years ago)
Author:
Collin Anderson
Comment:

Changed things for 1.9

Legend:

Unmodified
Added
Removed
Modified

  • Version1.9Roadmap

    v1 v2  
    33
    44==================
    5 Django 1.8 Roadmap
     5Django 1.9 Roadmap
    66==================
    77
    8 This document details the schedule and roadmap towards Django 1.8.
     8This document details the schedule and roadmap towards Django 1.9.
    99
    10 What features will be in Django 1.8?
     10What features will be in Django 1.9?
    1111====================================
    1212
    1313Whatever gets committed by the alpha feature freeze!
    1414
    15 Django 1.8 will be a fully time-based release; any features completed and committed to master by the alpha feature freeze deadline noted below will be included. Any that miss the deadline won't.
     15Django 1.9 will be a fully time-based release; any features completed and committed to master by the alpha feature freeze deadline noted below will be included. Any that miss the deadline won't.
    1616
    1717The Django core team has a couple of major features we'd like to merge:
    1818
    19 * `contrib.postgres - Marc Tamlyn <http://postgres.mjtamlyn.co.uk/>`_
    20 * `multiple template engines - Aymeric Augustin <https://myks.org/en/multiple-template-engines-for-django/>`_
    21 * `model _meta API - Daniel Pyrathon (GSoC project) <https://code.djangoproject.com/wiki/new_meta_api>`_
    22 * `Use F() objects in aggregates(), annotates() and values() - Josh Smeaton <https://code.djangoproject.com/ticket/14030>`_
     19* TBD
    2320
    2421Minor features and bug fixes will be committed as they are completed. If you have submitted a patch, be sure the flags on the Trac ticket are correct such that it appears in the "Patches needing review" filter of the `Django Development Dashboard <https://dashboard.djangoproject.com/>`_. Better yet, find someone to review your patch and mark the ticket as "Ready for checkin". Core developers try to regularly review and merge "Ready for checkin" tickets.
    … …  
    2724========
    2825
    29 Major milestones along the way to 1.8 are scheduled below. See `Process`_,
     26Major milestones along the way to 1.9 are scheduled below. See `Process`_,
    3027below, for more details. The dates are subject to change as necessary.
    3128
    3229==================  =============================================================
    33 Jan. 12, 2015       Django 1.8 alpha; feature freeze.
     30<TBD>       Django 1.9 alpha; feature freeze.
    3431
    35 Feb. 16             Django 1.8 beta; non-release blocking bug fix freeze.
     32<TBD>       Django 1.9 beta; non-release blocking bug fix freeze.
    3633
    37 March 16            Django 1.8 RC 1; translation string freeze.
     34<TBD>       Django 1.9 RC 1; translation string freeze.
    3835
    39 2+ weeks after RC1  Django 1.8 final (or RC 2, if needed).
     362+ weeks after RC1  Django 1.9 final (or RC 2, if needed).
    4037==================  =============================================================
    4138
    … …  
    4340=======
    4441
    45 Any features not completed by the feature freeze date won't make it into 1.8.
     42Any features not completed by the feature freeze date won't make it into 1.9.
    4643
    47 Tim Graham, as the release manager, will be in charge of keeping the schedule. The release manager keeps track of who's working on what issues so that bug reports can be efficiently routed and also nag developers who are in danger of missing deadlines. Marc Tamlyn will serve as a backup release manager.
     44<TBD> as the release manager, will be in charge of keeping the schedule. The release manager keeps track of who's working on what issues so that bug reports can be efficiently routed and also nag developers who are in danger of missing deadlines. <TBD> will serve as a backup release manager.
    4845
    4946Feature freeze / Alpha 1
    5047------------------------
    5148
    52 All major and minor features must be committed by the Alpha 1 deadline. Any features not done by this point will be deferred or dropped. Note that in past release cycles minor features were allowed until beta.
     49All major and minor features must be committed by the Alpha 1 deadline. Any features not done by this point will be deferred or dropped. Note that in the 1.6 and 1.7 release cycles minor features were allowed until beta.
    5350
    54 At this time, we will fork ``stable/1.8.x`` from ``master``. In previous release cycles we forked after beta, but now that we aren't going to accept minor features after alpha, we need to fork sooner.
     51At this time, we will fork ``stable/1.9.x`` from ``master``. In previous release cycles we forked after beta, but now that we aren't going to accept minor features after alpha, we need to fork sooner.
    5552
    5653After the alpha, non-release blocking bug fixes may be backported at the committer's discretion.
    57 
    58 There are a couple of code refactorings that ideally should be done near the alpha deadline before we fork ``stable/1.8.x``. They are tagged in Trac with `1.8-alpha <https://code.djangoproject.com/query?status=!closed&keywords=~1.8-alpha>`_.
    5954
    6055Beta 1
    … …  
    7368-----
    7469
    75 Ideally, Django 1.8 final will ship two weeks after the last RC. If there are no major bugs found by 2 weeks after the release candidate, we will issue 1.8 final. If not, we will decide how to proceed from there at that time (likely another release candidate would be issue at some point).
     70Ideally, Django 1.9 final will ship two weeks after the last RC. If there are no major bugs found by 2 weeks after the release candidate, we will issue 1.9 final. If not, we will decide how to proceed from there at that time (likely another release candidate would be issue at some point).
    7671
    7772How you can help
Back to Top