Changes between Version 3 and Version 4 of Version1.8Roadmap
- Timestamp:
- Oct 20, 2014, 10:14:56 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Version1.8Roadmap
v3 v4 8 8 This document details the schedule and roadmap towards Django 1.8. 9 9 10 What will be in Django 1.8?11 =========================== 10 What features will be in Django 1.8? 11 ==================================== 12 12 13 Whatever gets committed by TBA!13 Whatever gets committed by the alpha feature freeze! 14 14 15 Django 1.8 will be a fully time-based release; any features completed and checked in by the feature freeze deadline (TBA) will be included. Any that miss the deadline won't. 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. 16 16 17 The Django core team has a couple of major features we'd like to merge: 17 18 18 19 * contrib.postgres - Marc Tamlyn 19 20 * multiple template engines - Aymeric Augustin 20 * model `_meta`API - Daniel Pyrathon (GSoC project)21 * Use `F()` objects in `aggregates()`, `annotates()` and `values()`- Josh Smeaton21 * model _meta API - Daniel Pyrathon (GSoC project) 22 * Use F() objects in aggregates(), annotates() and values() - Josh Smeaton 22 23 23 Minor 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". 24 Minor 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. 24 25 25 26 Schedule … … 30 31 31 32 ================== ============================================================= 32 TBA Django 1.8 alpha; majorfeature freeze.33 Jan. 12, 2015 Django 1.8 alpha; feature freeze. 33 34 34 TBA Django 1.8 beta; complete featurefreeze.35 Feb. 16 Django 1.8 beta; non-release blocking bug fix freeze. 35 36 36 TBADjango 1.8 RC 1; translation string freeze.37 March 16 Django 1.8 RC 1; translation string freeze. 37 38 38 2+ weeks after RC1 39 2+ weeks after RC1 Django 1.8 final (or RC 2, if needed). 39 40 ================== ============================================================= 40 41 … … 42 43 ======= 43 44 44 Any code not complete by feature freeze dateswon't make it into 1.8.45 Any features not completed by the feature freeze date won't make it into 1.8. 45 46 46 XXX, 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. XXXwill serve as a backup release manager.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. 47 48 48 49 Feature freeze / Alpha 1 49 50 ------------------------ 50 51 51 All major features must be committed by the Alpha 1 deadline. Any 52 work not done by this point will be deferred or dropped. 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. 53 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. 55 56 After 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>`_. 53 59 54 60 Beta 1 55 61 ------ 56 62 57 Beta 1 marks the end of *any* feature work. Only bug fixes will be allowed in after this point.63 Beta 1 marks the end of any changes that aren't considered release blocking bugs. A bug is a "Release blocker" if it's a regression from a previous version of Django or if it's an important bug in a new feature. Only release blocking bug fixes will be allowed to be backported after the beta. 58 64 59 65 RC 1 60 66 ---- 61 67 62 RC 1 will become the final release if no bugs are found; there is a total code freeze after this point, unless a new RC is needed.68 If there is still a consistent stream of release blockers coming in at the planned release candidate date; we'll release beta 2 to encourage further testing and push the release candidate date out ~1 month. 63 69 64 RC 1 also marks string freeze; translators will have two weeks to submit updated translations for inclusion in the final release.70 RC 1 marks the freeze for translation strings; translators will have two weeks to submit updated translations for inclusion in the final release. Release blocking bug fixes may continue to be backported. 65 71 66 Release 67 ------- 68 Django 1.8 final will ship two weeks after the last RC. Hopefully we'll only need 69 a single RC, so, the final release will follow roughly a week after RC 1. If 70 blockers are found, another RC will be released instead. 72 Final 73 ----- 74 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). 71 76 72 77 How you can help … … 78 83 * Read the `guide to contributing to Django <http://docs.djangoproject.com/en/dev/internals/contributing/>`_ and the `guide to Django's 79 84 release process <http://docs.djangoproject.com/en/dev/internals/release-process/>`_. 80 85 81 86 These guides explains how our process works. where to ask questions, 82 87 etc. It'll save everyone time if we're all on the same page when it 83 88 comes to process. 84 89 85 90 * Work on patches and `triage tickets <https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/>`_. 86 91 87 92 * Attend a sprint (in person or in IRC). 88 93 89 94 * Test the release snapshots (alphas, betas) against your code and report 90 95 bugs. 91 96 92 97 * We need *lots* of testers if we're to have a bug-free release. Download 93 98 a snapshot or a git checkout and give it a try!