Changes between Version 7 and Version 8 of VersionOneRoadmap
- Timestamp:
- Jun 25, 2008, 10:12:26 AM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
VersionOneRoadmap
v7 v8 8 8 This document details the schedule and roadmap towards Django 1.0. All the details are below, but here's the executive summary: 9 9 10 * Django 1.0 will be released in `early September`__ 10 * Django 1.0 will be released in `early September`__. 11 11 12 12 * To meet that deadline, Django 1.0 has a minimal set of `must-have … … 23 23 24 24 __ `dates`_ 25 26 .. contents:: Table of Contents 25 27 26 28 What will be in 1.0? … … 59 61 Nothing in Django 1.0 should rely on the deprecated ``oldforms`` package. 60 62 We'll need to replace ``oldforms`` usage in generic views, and in 61 ``django.contrib.auth`` 63 ``django.contrib.auth``. 62 64 63 65 ``django.contrib.comments`` still uses ``oldforms`` as well, but … … 246 248 process. 247 249 248 * Work from the list above.250 * Work on features from the list above. 249 251 250 252 Get in touch with the lieutenant/committer for the feature you'd like … … 262 264 release. Lots of work gets done at sprints, and there's usually someone 263 265 around willing to help new developers get started. 264 266 267 * Organize tickets. 268 269 * `Must-have feature`__ bugs go in the "1.0 alpha" milestone. These basically 270 should be all nfa-blocker tickets. **Bugs** in the must-have features 271 are **not** to be part of this milestone; they can be fixed after the 272 alpha and should be put in the "1.0" milestone. 273 274 * Any **feature** tickets related to the `maybe list`__ get put in the "1.0 beta" 275 milestone. 276 277 * Any remaining **bugs** go in the "1.0" milestone. 278 265 279 * Test the release snapshots (alphas, betas) against your code and report 266 280 bugs. … … 270 284 271 285 __ http://www.djangoproject.com/documentation/contributing/ 286 __ `Must-have features`_ 287 __ `"Maybe" features`_ 272 288 273 289 Notes and miscellany