Django

Code

Changeset 8039

Show
Ignore:
Timestamp:
07/21/08 21:33:16 (6 months ago)
Author:
gwilson
Message:

Changed "each" to "ease" and made several edits from Adrian.

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • django/trunk/docs/release_notes_1.0_alpha.txt

    r8038 r8039  
    3939    this drastically simplifies the task of dealing with 
    4040    non-Western-European content and data in Django. Additionally, 
    41     utility functions have been provided to each interoperability with 
     41    utility functions have been provided to ease interoperability with 
    4242    third-party libraries and systems which may or may not handle 
    4343    Unicode gracefully. Details are available in Django's 
     
    6363    To provide improved security against cross-site scripting (XSS) 
    6464    vulnerabilities, Django's template system now automatically 
    65     escapes the output of variables; this behavior is configurable, 
     65    escapes the output of variables. This behavior is configurable, 
    6666    and allows both variables and larger template constructs to be 
    6767    marked as safe (requiring no escaping) or unsafe (requiring 
     
    7272 
    7373There are many more new features, many bugfixes and many enhancements 
    74 to existing features from previous releases; the ``newforms`` library, 
     74to existing features from previous releases. The ``newforms`` library, 
    7575for example, has undergone massive improvements including several 
    7676useful add-ons in ``django.contrib`` which complement and build on 
     
    7979uploading process as well as streaming uploads of large files. 
    8080 
    81 Along with these improvements and additions, there have been a number 
    82 of backwards-incompatible changes as features in Django have been 
     81Along with these improvements and additions, we've made a number of 
     82of backwards-incompatible changes to the framework, as features have been 
    8383fleshed out and APIs have been finalized for the 1.0 release. A 
    8484complete guide to these changes will be available as part of the final 
     
    9595One of the primary goals of this alpha release is to focus attention 
    9696on the remaining features to be implemented for Django 1.0, and on the 
    97 bugs which need to be resolved before the final release. Following 
     97bugs that need to be resolved before the final release. Following 
    9898this release, we'll be conducting a series of sprints building up to a 
    99 series of beta releases and finally a release-candidate stage, 
    100 followed soon after by Django 1.0. The timeline is projected to be: 
     99series of beta releases and a release-candidate stage, followed soon 
     100after by Django 1.0. The timeline is projected to be: 
    101101 
    102 * August 1, 2008: Sprint (based in Washington, D.C. and online). 
     102* August 1, 2008: Sprint (based in Washington, DC, and online). 
    103103 
    104104* August 5, 2008: Django 1.0 beta 1 release. This will also constitute 
    105   the feature freeze for 1.0; any feature to be included in 1.0 must 
     105  the feature freeze for 1.0. Any feature to be included in 1.0 must 
    106106  be completed and in trunk by this time. 
    107107 
    108 * August 8, 2008: Sprint (based in Lawrence, KS and online). 
     108* August 8, 2008: Sprint (based in Lawrence, KS, and online). 
    109109 
    110110* August 12, 2008: Django 1.0 beta 2 release. 
    111111 
    112 * August 15, 2008: Sprint (based in Austin, TX and online). 
     112* August 15, 2008: Sprint (based in Austin, TX, and online). 
    113113 
    114114* August 19, 2008: Django 1.0 release candidate 1. 
    115115 
    116 * August 22, 2008: Sprint (based in Portland, OR and online). 
     116* August 22, 2008: Sprint (based in Portland, OR, and online). 
    117117 
    118118* August 26, 2008: Django 1.0 release candidate 2. 
     
    120120* September 2, 2008: Django 1.0 final release. The official Django 1.0 
    121121  release party will take place during the first-ever DjangoCon, to be 
    122   held in Mountain View, CA September 6-7. 
     122  held in Mountain View, CA, September 6-7. 
    123123 
    124 Of course, like any estimated timeline this is subject to change as 
    125 requirements dictate; the latest information will always be available 
     124Of course, like any estimated timeline, this is subject to change as 
     125requirements dictate. The latest information will always be available 
    126126on the Django project wiki: 
    127127 
     
    137137codebase in a safe test environment and reporting any bugs or issues 
    138138you encounter. The Django ticket tracker is the central place to 
    139 search for open issues and open new issues if no existing ticket 
    140 corresponds to a problem you're running into: 
     139search for open issues: 
    141140 
    142141    http://code.djangoproject.com/timeline 
     142 
     143Please open new tickets if no existing ticket corresponds to a problem 
     144you're running into. 
    143145 
    144146Additionally, discussion of Django development, including progress 
     
    148150    http://groups.google.com/group/django-developers 
    149151 
    150 And in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If 
     152...and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If 
    151153you're interested in helping out with Django's development, feel free 
    152 to join the discussions there. Django's online documentation also 
    153 includes pointers on how to contribute to Django: 
     154to join the discussions there. 
     155 
     156Django's online documentation also includes pointers on how to 
     157contribute to Django: 
    154158 
    155159    http://www.djangoproject.com/documentation/contributing/ 
    156160 
    157 Contributions on any level -- from developing code to writing 
    158 documentation to simply triaging tickets and helping to test proposed 
    159 bugfixes -- are always welcome and always appreciated. 
     161Contributions on any level -- developing code, writing 
     162documentation or simply triaging tickets and helping to test proposed 
     163bugfixes -- are always welcome and appreciated.