PageRenderTime 38ms CodeModel.GetById 26ms RepoModel.GetById 0ms app.codeStats 0ms

Plain Text | 101 lines | 75 code | 26 blank | 0 comment | 0 complexity | cc7c5d7589dbed9e55aeb5736a66640f MD5 | raw file
Possible License(s): BSD-3-Clause
  1. =============================
  2. Django 1.2 RC 1 release notes
  3. =============================
  4. May 5, 2010
  5. Welcome to the first Django 1.2 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.2. This release is targeted primarily at developers who are
  9. interested in trying out new features and testing the Django codebase
  10. to help identify and resolve any critical bugs prior to the final 1.2
  11. release.
  12. As such, this release is not yet intended for production use, and any
  13. such use is discouraged.
  14. Django has been feature frozen since the 1.2 beta release, so this
  15. release candidate contains no new features, only bugfixes; for a
  16. summary of features new to Django 1.2, consult the :doc:`1.2 alpha
  17. </releases/1.2-alpha-1>` and :doc:`1.2 beta </releases/1.2-beta-1>`
  18. release notes.
  19. Python compatibility
  20. ====================
  21. While not a new feature, it's important to note that Django 1.2
  22. introduces the first shift in our Python compatibility policy since
  23. Django's initial public debut. Previous Django releases were tested
  24. and supported on 2.x Python versions from 2.3 up; Django 1.2, however,
  25. drops official support for Python 2.3. As such, the minimum Python
  26. version required for Django is now 2.4, and Django is tested and
  27. supported on Python 2.4, 2.5 and 2.6, and will be supported on the
  28. as-yet-unreleased Python 2.7.
  29. This change should affect only a small number of Django users, as most
  30. operating-system vendors today are shipping Python 2.4 or newer as
  31. their default version. If you're still using Python 2.3, however,
  32. you'll need to stick to Django 1.1 until you can upgrade; per
  33. :doc:`our support policy </internals/release-process>`, Django 1.1 will
  34. continue to receive security support until the release of Django 1.3.
  35. A roadmap for Django's overall 2.x Python support, and eventual
  36. transition to Python 3.x, is currently being developed, and will be
  37. announced prior to the release of Django 1.3.
  38. The Django 1.2 roadmap
  39. ======================
  40. As of this release candidate, Django 1.2 is in both feature freeze and
  41. "string freeze" -- all strings marked for translation in the Django
  42. codebase will retain their current form in the final Django 1.2
  43. release. Only critical release-blocking bugs, documentation and
  44. updated translation files will receive attention between now and the
  45. final 1.2 release. Note that Django's localization infrastructure has
  46. been expanded for 1.2, and translation packages should now include a
  47. ```` file containing data for localized formatting of
  48. numbers and dates.
  49. If no critical bugs are discovered, Django 1.2 will be released
  50. approximately one week after this release candidate, on or about May
  51. 12, 2010.
  52. What you can do to help
  53. =======================
  54. In order to provide a high-quality 1.2 release, we need your
  55. help. Although this release candidate is, again, *not* intended for
  56. production use, you can help the Django team by trying out this
  57. release candidate in a safe testing environment and reporting any bugs
  58. or issues you encounter. The Django ticket tracker is the central
  59. place to search for open issues:
  60. *
  61. Please open a new ticket only if no existing ticket corresponds to a
  62. problem you're running into.
  63. Additionally, discussion of Django development, including progress
  64. toward the 1.2 release, takes place daily on the django-developers
  65. mailing list:
  66. *
  67. ... and in the ``#django-dev`` IRC channel on ````. If you're
  68. interested in helping out with Django's development, feel free to join the
  69. discussions there.
  70. Django's online documentation also includes pointers on how to contribute to
  71. Django:
  72. * :doc:`How to contribute to Django </internals/contributing>`
  73. Contributions on any level -- developing code, writing documentation or simply
  74. triaging tickets and helping to test proposed bugfixes -- are always welcome and
  75. appreciated.