PageRenderTime 37ms CodeModel.GetById 25ms RepoModel.GetById 0ms app.codeStats 1ms

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