PageRenderTime 42ms CodeModel.GetById 14ms RepoModel.GetById 1ms app.codeStats 0ms

Plain Text | 119 lines | 93 code | 26 blank | 0 comment | 0 complexity | 1ae3b6969c1c69f962d6df5ce501a26c MD5 | raw file
Possible License(s): BSD-3-Clause
  1. ===============================
  2. Django 1.0 beta 2 release notes
  3. ===============================
  4. Welcome to Django 1.0 beta 2!
  5. This is the fourth in a series of preview/development releases leading
  6. up to the eventual release of Django 1.0, currently scheduled to take
  7. place in early September 2008. This releases is primarily targeted at
  8. developers who are interested in testing the Django codebase and
  9. helping to identify and resolve bugs prior to the final 1.0 release.
  10. As such, this release is *not* intended for production use, and any
  11. such use is discouraged.
  12. What's new in Django 1.0 beta 2
  13. ===============================
  14. Django's development trunk has been the site of nearly constant
  15. activity over the past year, with several major new features landing
  16. since the 0.96 release. For features which were new as of Django 1.0
  17. alpha 1, see :doc:`the 1.0 alpha 1 release notes
  18. </releases/1.0-alpha-1>`. For features which were new as of Django 1.0
  19. alpha 2, see :doc:`the 1.0 alpha 2 release notes
  20. </releases/1.0-alpha-2>`. For features which were new as of Django 1.0
  21. beta 1, see :doc:`the 1.0 beta 1 release notes </releases/1.0-beta>`.
  22. This beta release includes two major features:
  23. Refactored ``django.contrib.comments``
  24. As part of a Google Summer of Code project, Thejaswi Puthraya
  25. carried out a major rewrite and refactoring of Django's bundled
  26. comment system, greatly increasing its flexibility and
  27. customizability. :doc:`Full documentation
  28. </ref/contrib/comments/index>` is available, as well as :doc:`an
  29. upgrade guide </ref/contrib/comments/upgrade>` if you were using
  30. the previous incarnation of the comments application..
  31. Refactored documentation
  32. Django's bundled and online documentation has also been
  33. significantly refactored; the new documentation system uses
  34. `Sphinx`_ to build the docs and handle such niceties as topical
  35. indexes, reference documentation and cross-references within the
  36. docs. You can check out the new documentation `online`_ or, if you
  37. have Sphinx installed, build the HTML yourself from the
  38. documentation files bundled with Django.
  39. .. _Sphinx:
  40. .. _online:
  41. Along with these new features, the Django team has also been hard at
  42. work polishing Django's codebase for the final 1.0 release; this beta
  43. release contains a large number of smaller improvements and bugfixes
  44. from the ongoing push to 1.0.
  45. Also, as part of its ongoing deprecation process, Django's old
  46. form-handling system has been removed; this means ``django.oldforms``
  47. no longer exists, and its various API hooks (such as automatic
  48. manipulators) are no longer present in Django. This system has been
  49. completely replaced by :doc:`the new form-handling system
  50. </topics/forms/index>` in ``django.forms``.
  51. The Django 1.0 roadmap
  52. ======================
  53. One of the primary goals of this beta release is to focus attention on
  54. the remaining features to be implemented for Django 1.0, and on the
  55. bugs that need to be resolved before the final release. As of this
  56. beta release, Django is in its final "feature freeze" for 1.0; feature
  57. requests will be deferred to later releases, and the development
  58. effort will be focused solely on bug-fixing and stability. Django is
  59. also now in a "string freeze"; translatable strings (labels, error
  60. messages, etc.) in Django's codebase will not be changed prior to the
  61. release, in order to allow our translators to produce the final 1.0
  62. version of Django's translation files.
  63. Following this release, we'll be conducting a final development sprint
  64. on August 30, 2008, based in London and coordinated online; the goal
  65. of this sprint will be to squash as many bugs as possible in
  66. anticipation of the final 1.0 release, which is currently targeted for
  67. **September 2, 2008**. The official Django 1.0 release party will take
  68. place during the first-ever DjangoCon, to be held in Mountain View,
  69. California, USA, September 6-7.
  70. What you can do to help
  71. =======================
  72. In order to provide a high-quality 1.0 release, we need your
  73. help. Although this beta release is, again, *not* intended for
  74. production use, you can help the Django team by trying out the beta
  75. codebase in a safe test environment and reporting any bugs or issues
  76. you encounter. The Django ticket tracker is the central place to
  77. search for open issues:
  79. Please open new tickets if no existing ticket corresponds to a problem
  80. you're running into.
  81. Additionally, discussion of Django development, including progress
  82. toward the 1.0 release, takes place daily on the django-developers
  83. mailing list:
  85. ...and in the ``#django-dev`` IRC channel on ````. If
  86. you're interested in helping out with Django's development, feel free
  87. to join the discussions there.
  88. Django's online documentation also includes pointers on how to
  89. contribute to Django:
  90. :doc:`contributing to Django </internals/contributing>`
  91. Contributions on any level -- developing code, writing
  92. documentation or simply triaging tickets and helping to test proposed
  93. bugfixes -- are always welcome and appreciated.