PageRenderTime 63ms CodeModel.GetById 58ms app.highlight 1ms RepoModel.GetById 1ms app.codeStats 0ms

/docs/releases/1.1-rc-1.txt

https://code.google.com/p/mango-py/
Plain Text | 109 lines | 80 code | 29 blank | 0 comment | 0 complexity | fd28ca35a77f9c1c478e0963abc41784 MD5 | raw file
  1=============================
  2Django 1.1 RC 1 release notes
  3=============================
  4
  5
  6July 21, 2009
  7
  8Welcome to the first Django 1.1 release candidate!
  9
 10This is the third -- and likely last -- in a series of
 11preview/development releases leading up to the eventual release of
 12Django 1.1, currently scheduled to take place approximately one week
 13after this release candidate. This release is targeted primarily at
 14developers who are interested in trying out new features and testing
 15the Django codebase to help identify and resolve any critical bugs
 16prior to the final 1.1 release.
 17
 18As such, this release is not yet intended for production use, and any
 19such use is discouraged.
 20
 21
 22What's new in Django 1.1 RC 1
 23=============================
 24
 25The Django codebase has -- with one exception -- been in feature
 26freeze since the first 1.1 beta release, and so this release candidate
 27contains only one new feature (see below); work leading up to this
 28release candidate has instead been focused on bugfixing, particularly
 29on the new features introduced prior to the 1.1 beta.
 30
 31For an overview of those features, consult :doc:`the Django 1.1 beta
 32release notes </releases/1.1-beta-1>`.
 33
 34
 35URL namespaces
 36--------------
 37
 38The 1.1 beta release introduced the ability to use reverse URL
 39resolution with Django's admin application, which exposed a set of
 40:ref:`named URLs <naming-url-patterns>`. Unfortunately, achieving
 41consistent and correct reverse resolution for admin URLs proved
 42extremely difficult, and so one additional feature was added to Django
 43to resolve this issue: URL namespaces.
 44
 45In short, this feature allows the same group of URLs, from the same
 46application, to be included in a Django URLConf multiple times, with
 47varying (and potentially nested) named prefixes which will be used
 48when performing reverse resolution. For full details, see :ref:`the
 49documentation on defining URL namespaces
 50<topics-http-defining-url-namespaces>`.
 51
 52Due to the changes needed to support this feature, the URL pattern
 53names used when reversing admin URLs have changed since the 1.1 beta
 54release; if you were developing applications which took advantage of
 55this new feature, you will need to update your code to reflect the new
 56names (for most purposes, changing ``admin_`` to ``admin:`` in names
 57to be reversed will suffice). For a full list of URL pattern names
 58used by the admin and information on how namespaces are applied to
 59them, consult the documentation on :ref:`reversing admin URLs
 60<admin-reverse-urls>`.
 61
 62
 63The Django 1.1 roadmap
 64======================
 65
 66As of this release candidate, Django 1.1 is in both feature freeze and
 67"string freeze" -- all strings marked for translation in the Django
 68codebase will retain their current form in the final Django 1.1
 69release. Only critical release-blocking bugs will receive attention
 70between now and the final 1.1 release.
 71
 72If no such bugs are discovered, Django 1.1 will be released
 73approximately one week after this release candidate, on or about July
 7428, 2009.
 75
 76
 77What you can do to help
 78=======================
 79
 80In order to provide a high-quality 1.1 release, we need your
 81help. Although this release candidate is, again, *not* intended for
 82production use, you can help the Django team by trying out this
 83release candidate in a safe testing environment and reporting any bugs
 84or issues you encounter. The Django ticket tracker is the central
 85place to search for open issues:
 86
 87    * http://code.djangoproject.com/timeline
 88
 89Please open a new ticket only if no existing ticket corresponds to a
 90problem you're running into.
 91
 92Additionally, discussion of Django development, including progress
 93toward the 1.1 release, takes place daily on the django-developers
 94mailing list:
 95
 96    * http://groups.google.com/group/django-developers
 97
 98... and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If you're
 99interested in helping out with Django's development, feel free to join the
100discussions there.
101
102Django's online documentation also includes pointers on how to contribute to
103Django: 
104
105    * :doc:`How to contribute to Django </internals/contributing>`
106
107Contributions on any level -- developing code, writing documentation or simply
108triaging tickets and helping to test proposed bugfixes -- are always welcome and
109appreciated.