Changeset 8039
- Timestamp:
- 07/21/08 21:33:16 (6 months ago)
- Files:
-
- django/trunk/docs/release_notes_1.0_alpha.txt (modified) (8 diffs)
Legend:
- Unmodified
- Added
- Removed
- Modified
- Copied
- Moved
django/trunk/docs/release_notes_1.0_alpha.txt
r8038 r8039 39 39 this drastically simplifies the task of dealing with 40 40 non-Western-European content and data in Django. Additionally, 41 utility functions have been provided to ea chinteroperability with41 utility functions have been provided to ease interoperability with 42 42 third-party libraries and systems which may or may not handle 43 43 Unicode gracefully. Details are available in Django's … … 63 63 To provide improved security against cross-site scripting (XSS) 64 64 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, 66 66 and allows both variables and larger template constructs to be 67 67 marked as safe (requiring no escaping) or unsafe (requiring … … 72 72 73 73 There are many more new features, many bugfixes and many enhancements 74 to existing features from previous releases ; the ``newforms`` library,74 to existing features from previous releases. The ``newforms`` library, 75 75 for example, has undergone massive improvements including several 76 76 useful add-ons in ``django.contrib`` which complement and build on … … 79 79 uploading process as well as streaming uploads of large files. 80 80 81 Along with these improvements and additions, there have been a number82 of backwards-incompatible changes as features in Djangohave been81 Along with these improvements and additions, we've made a number of 82 of backwards-incompatible changes to the framework, as features have been 83 83 fleshed out and APIs have been finalized for the 1.0 release. A 84 84 complete guide to these changes will be available as part of the final … … 95 95 One of the primary goals of this alpha release is to focus attention 96 96 on the remaining features to be implemented for Django 1.0, and on the 97 bugs whichneed to be resolved before the final release. Following97 bugs that need to be resolved before the final release. Following 98 98 this 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 soonafter by Django 1.0. The timeline is projected to be:99 series of beta releases and a release-candidate stage, followed soon 100 after by Django 1.0. The timeline is projected to be: 101 101 102 * August 1, 2008: Sprint (based in Washington, D .C.and online).102 * August 1, 2008: Sprint (based in Washington, DC, and online). 103 103 104 104 * 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 must105 the feature freeze for 1.0. Any feature to be included in 1.0 must 106 106 be completed and in trunk by this time. 107 107 108 * August 8, 2008: Sprint (based in Lawrence, KS and online).108 * August 8, 2008: Sprint (based in Lawrence, KS, and online). 109 109 110 110 * August 12, 2008: Django 1.0 beta 2 release. 111 111 112 * August 15, 2008: Sprint (based in Austin, TX and online).112 * August 15, 2008: Sprint (based in Austin, TX, and online). 113 113 114 114 * August 19, 2008: Django 1.0 release candidate 1. 115 115 116 * August 22, 2008: Sprint (based in Portland, OR and online).116 * August 22, 2008: Sprint (based in Portland, OR, and online). 117 117 118 118 * August 26, 2008: Django 1.0 release candidate 2. … … 120 120 * September 2, 2008: Django 1.0 final release. The official Django 1.0 121 121 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. 123 123 124 Of course, like any estimated timeline this is subject to change as125 requirements dictate ; the latest information will always be available124 Of course, like any estimated timeline, this is subject to change as 125 requirements dictate. The latest information will always be available 126 126 on the Django project wiki: 127 127 … … 137 137 codebase in a safe test environment and reporting any bugs or issues 138 138 you 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: 139 search for open issues: 141 140 142 141 http://code.djangoproject.com/timeline 142 143 Please open new tickets if no existing ticket corresponds to a problem 144 you're running into. 143 145 144 146 Additionally, discussion of Django development, including progress … … 148 150 http://groups.google.com/group/django-developers 149 151 150 And in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If152 ...and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If 151 153 you'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: 154 to join the discussions there. 155 156 Django's online documentation also includes pointers on how to 157 contribute to Django: 154 158 155 159 http://www.djangoproject.com/documentation/contributing/ 156 160 157 Contributions on any level -- from developing code towriting158 documentation tosimply triaging tickets and helping to test proposed159 bugfixes -- are always welcome and a lways appreciated.161 Contributions on any level -- developing code, writing 162 documentation or simply triaging tickets and helping to test proposed 163 bugfixes -- are always welcome and appreciated.
