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