PageRenderTime 44ms CodeModel.GetById 16ms RepoModel.GetById 0ms app.codeStats 0ms

Plain Text | 136 lines | 101 code | 35 blank | 0 comment | 0 complexity | a3f2cf06c550f838d5b6b88c3a6bc943 MD5 | raw file
Possible License(s): BSD-3-Clause
  1. ================================
  2. Django 1.0 alpha 2 release notes
  3. ================================
  4. Welcome to Django 1.0 alpha 2!
  5. This is the second 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 strongly discouraged.
  12. What's new in Django 1.0 alpha 2
  13. ================================
  14. Django's development trunk has been the site of nearly constant activity over
  15. the past year, with several major new features landing since the 0.96 release.
  16. For features which were new as of Django 1.0 alpha 1, see :doc:`the 1.0 alpha 1
  17. release notes </releases/1.0-alpha-1>`. Since the 1.0 alpha 1 release several new
  18. features have landed, including:
  19. ``django.contrib.gis`` (`GeoDjango`_)
  20. A project over a year in the making, this adds world-class GIS
  21. (`Geographic Information Systems`_) support to Django, in the form
  22. of a ``contrib`` application. `Its documentation`_ is currently
  23. being maintained externally, and will be merged into the main
  24. Django documentation prior to the final 1.0 release. Huge thanks
  25. go to Justin Bronn, Jeremy Dunck, Brett Hoerner and Travis Pinney
  26. for their efforts in creating and completing this feature.
  27. Pluggable file storage
  28. Django's built-in ``FileField`` and ``ImageField`` now can take advantage of
  29. pluggable file-storage backends, allowing extensive customization of where
  30. and how uploaded files get stored by Django. For details, see :doc:`the
  31. files documentation </topics/files>`; big thanks go to Marty Alchin for
  32. putting in the hard work to get this completed.
  33. Jython compatibility
  34. Thanks to a lot of work from Leo Soto during a Google Summer of
  35. Code project, Django's codebase has been refactored to remove
  36. incompatibilities with `Jython`_, an implementation of Python
  37. written in Java, which runs Python code on the Java Virtual
  38. Machine. Django is now compatible with the forthcoming Jython 2.5
  39. release.
  40. There are many other new features and improvements in this release, including
  41. two major performance boosts: strings marked for translation using
  42. :doc:`Django's internationalization system </topics/i18n/index>` now consume far less
  43. memory, and Django's internal dispatcher -- which is invoked frequently during
  44. request/response processing and when working with Django's object-relational
  45. mapper -- is now significantly faster.
  46. .. _GeoDjango:
  47. .. _Geographic Information Systems:
  48. .. _Its documentation:
  49. .. _Jython:
  50. The Django 1.0 roadmap
  51. ======================
  52. One of the primary goals of this alpha release is to focus attention
  53. on the remaining features to be implemented for Django 1.0, and on the
  54. bugs that need to be resolved before the final release. Following this
  55. release, we'll be conducting a series of development sprints building
  56. up to the beta and release-candidate stages, followed soon after by
  57. Django 1.0. The timeline is projected to be:
  58. * **August 14, 2008: Django 1.0 beta release.** Past this point Django
  59. will be in a "feature freeze" for the 1.0 release; after Django 1.0
  60. beta, the development focus will be solely on bug fixes and
  61. stabilization.
  62. * August 15, 2008: Sprint (based in Austin, Texas, USA, and online).
  63. * August 17, 2008: Sprint (based in Tel Aviv, Israel, and online).
  64. * **August 21, 2008: Django 1.0 release candidate 1.** At this point,
  65. all strings marked for translation within Django's codebase will be
  66. frozen, to provide contributors time to check and finalize all of
  67. Django's bundled translation files prior to the final 1.0 release.
  68. * August 22, 2008: Sprint (based in Portland, Oregon, USA, and online).
  69. * **August 26, 2008: Django 1.0 release candidate 2.**
  70. * August 30, 2008: Sprint (based in London, England, UK, and online).
  71. * **September 2, 2008: Django 1.0 final release.** The official Django
  72. 1.0 release party will take place during the first-ever DjangoCon,
  73. to be held in Mountain View, California, USA, September 6-7.
  74. Of course, like any estimated timeline, this is subject to change as
  75. requirements dictate. The latest information will always be available
  76. on the Django project wiki:
  78. What you can do to help
  79. =======================
  80. In order to provide a high-quality 1.0 release, we need your
  81. help. Although this alpha release is, again, *not* intended for
  82. production use, you can help the Django team by trying out the alpha
  83. codebase in a safe test environment and reporting any bugs or issues
  84. you encounter. The Django ticket tracker is the central place to
  85. search for open issues:
  87. Please open new tickets if no existing ticket corresponds to a problem
  88. you're running into.
  89. Additionally, discussion of Django development, including progress
  90. toward the 1.0 release, takes place daily on the django-developers
  91. mailing list:
  93. ...and in the ``#django-dev`` IRC channel on ````. If
  94. you're interested in helping out with Django's development, feel free
  95. to join the discussions there.
  96. Django's online documentation also includes pointers on how to
  97. contribute to Django:
  98. :doc:`contributing to Django </internals/contributing>`
  99. Contributions on any level -- developing code, writing
  100. documentation or simply triaging tickets and helping to test proposed
  101. bugfixes -- are always welcome and appreciated.