Fixed #23692 -- Removed alpha/beta/rc release notes.

================================

Django 1.0 alpha release notes

================================

Welcome to Django 1.0 alpha!

This is the first in a series of preview/development releases leading

up to the eventual release of Django 1.0, currently scheduled to take

place in early September 2008. This release is primarily targeted at

developers who are interested in testing the Django codebase and

helping to identify and resolve bugs prior to the final 1.0 release.

As such, this release is *not* intended for production use, and any

such use is strongly discouraged.

What's new in Django 1.0 alpha

==============================

Django's development trunk has been the site of nearly constant

activity over the past year, with several major new features landing

since the 0.96 release. Some of the highlights include:

Refactored admin application (newforms-admin)

    The Django administrative interface (``django.contrib.admin``) has

    been completely refactored; admin definitions are now completely

    decoupled from model definitions (no more ``class Admin``

    declaration in models!), rewritten to use Django's new

    form-handling library (introduced in the 0.96 release as

    ``django.newforms``, and now available as simply ``django.forms``)

    and redesigned with extensibility and customization in mind. Full

    documentation for the admin application is available online in the

    official Django documentation:

    * :doc:`admin reference </ref/contrib/admin/index>`

Improved Unicode handling

    Django's internals have been refactored to use Unicode throughout;

    this drastically simplifies the task of dealing with

    non-Western-European content and data in Django. Additionally,

    utility functions have been provided to ease interoperability with

    third-party libraries and systems which may or may not handle

    Unicode gracefully. Details are available in Django's

    Unicode-handling documentation:

    * :doc:`unicode reference </ref/unicode>`

An improved Django ORM

    Django's object-relational mapper -- the component which provides

    the mapping between Django model classes and your database, and

    which mediates your database queries -- has been dramatically

    improved by a massive refactoring. For most users of Django this

    is backwards-compatible; the public-facing API for database

    querying underwent a few minor changes, but most of the updates

    took place in the ORM's internals. A guide to the changes,

    including backwards-incompatible modifications and mentions of new

    features opened up by this refactoring, is available on the Django

    wiki:

    * https://code.djangoproject.com/wiki/QuerysetRefactorBranch

Automatic escaping of template variables

    To provide improved security against cross-site scripting (XSS)

    vulnerabilities, Django's template system now automatically

    escapes the output of variables. This behavior is configurable,

    and allows both variables and larger template constructs to be

    marked as safe (requiring no escaping) or unsafe (requiring

    escaping). A full guide to this feature is in the documentation

    for the :ttag:`autoescape` tag.

There are many more new features, many bugfixes and many enhancements

to existing features from previous releases. The ``newforms`` library,

for example, has undergone massive improvements including several

useful add-ons in ``django.contrib`` which complement and build on

Django's form-handling capabilities, and Django's file-uploading

handlers have been refactored to allow finer-grained control over the

uploading process as well as streaming uploads of large files.

Along with these improvements and additions, we've made a number of

backwards-incompatible changes to the framework, as features have been

fleshed out and APIs have been finalized for the 1.0 release. A

complete guide to these changes will be available as part of the final

Django 1.0 release, and a comprehensive list of backwards-incompatible

changes is also available on the Django wiki for those who want to

begin developing and testing their upgrade process:

* https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges

The Django 1.0 roadmap

======================

One of the primary goals of this alpha release is to focus attention

on the remaining features to be implemented for Django 1.0, and on the

bugs that need to be resolved before the final release. Following

this release, we'll be conducting a series of sprints building up to a

series of beta releases and a release-candidate stage, followed soon

after by Django 1.0. The timeline is projected to be:

* August 1, 2008: Sprint (based in Washington, DC, and online).

* August 5, 2008: Django 1.0 beta 1 release. This will also constitute

  the feature freeze for 1.0. Any feature to be included in 1.0 must

  be completed and in trunk by this time.

* August 8, 2008: Sprint (based in Lawrence, KS, and online).

* August 12, 2008: Django 1.0 beta 2 release.

* August 15, 2008: Sprint (based in Austin, TX, and online).

* August 19, 2008: Django 1.0 release candidate 1.

* August 22, 2008: Sprint (based in Portland, OR, and online).

* August 26, 2008: Django 1.0 release candidate 2.

* September 2, 2008: Django 1.0 final release. The official Django 1.0

  release party will take place during the first-ever DjangoCon, to be

  held in Mountain View, CA, September 6-7.

Of course, like any estimated timeline, this is subject to change as

requirements dictate. The latest information will always be available

on the Django project wiki:

* https://code.djangoproject.com/wiki/VersionOneRoadmap

What you can do to help

=======================

In order to provide a high-quality 1.0 release, we need your

help. Although this alpha release is, again, *not* intended for

production use, you can help the Django team by trying out the alpha

codebase in a safe test environment and reporting any bugs or issues

you encounter. The Django ticket tracker is the central place to

search for open issues:

* https://code.djangoproject.com/timeline

Please open new tickets if no existing ticket corresponds to a problem

you're running into.

Additionally, discussion of Django development, including progress

toward the 1.0 release, takes place daily on the django-developers

mailing list:

* http://groups.google.com/group/django-developers

...and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If

you're interested in helping out with Django's development, feel free

to join the discussions there.

Django's online documentation also includes pointers on how to

contribute to Django:

* :doc:`contributing to Django </internals/contributing/index>`

Contributions on any level -- developing code, writing

documentation or simply triaging tickets and helping to test proposed

bugfixes -- are always welcome and appreciated.

================================

Django 1.0 alpha 2 release notes

================================

Welcome to Django 1.0 alpha 2!

This is the second in a series of preview/development releases leading

up to the eventual release of Django 1.0, currently scheduled to take

place in early September 2008. This releases is primarily targeted at

developers who are interested in testing the Django codebase and

helping to identify and resolve bugs prior to the final 1.0 release.

As such, this release is *not* intended for production use, and any

such use is strongly discouraged.

What's new in Django 1.0 alpha 2

================================

Django's development trunk has been the site of nearly constant activity over

the past year, with several major new features landing since the 0.96 release.

For features which were new as of Django 1.0 alpha 1, see :doc:`the 1.0 alpha 1

release notes </releases/1.0-alpha-1>`. Since the 1.0 alpha 1 release several new

features have landed, including:

``django.contrib.gis`` (`GeoDjango`_)

    A project over a year in the making, this adds world-class GIS

    (`Geographic Information Systems`_) support to Django, in the form

    of a ``contrib`` application. Its documentation is currently

    being maintained externally, and will be merged into the main

    Django documentation prior to the final 1.0 release. Huge thanks

    go to Justin Bronn, Jeremy Dunck, Brett Hoerner and Travis Pinney

    for their efforts in creating and completing this feature.

Pluggable file storage

    Django's built-in ``FileField`` and ``ImageField`` now can take advantage of

    pluggable file-storage backends, allowing extensive customization of where

    and how uploaded files get stored by Django. For details, see :doc:`the

    files documentation </topics/files>`; big thanks go to Marty Alchin for

    putting in the hard work to get this completed.

Jython compatibility

    Thanks to a lot of work from Leo Soto during a Google Summer of

    Code project, Django's codebase has been refactored to remove

    incompatibilities with `Jython`_, an implementation of Python

    written in Java, which runs Python code on the Java Virtual

    Machine. Django is now compatible with the forthcoming Jython 2.5

    release.

There are many other new features and improvements in this release, including

two major performance boosts: strings marked for translation using

:doc:`Django's internationalization system </topics/i18n/index>` now consume far less

memory, and Django's internal dispatcher -- which is invoked frequently during

request/response processing and when working with Django's object-relational

mapper -- is now significantly faster.

.. _GeoDjango: http://geodjango.org/

.. _Geographic Information Systems: http://en.wikipedia.org/wiki/Geographic_information_system

.. _Jython: http://www.jython.org/

The Django 1.0 roadmap

======================

One of the primary goals of this alpha release is to focus attention

on the remaining features to be implemented for Django 1.0, and on the

bugs that need to be resolved before the final release. Following this

release, we'll be conducting a series of development sprints building

up to the beta and release-candidate stages, followed soon after by

Django 1.0. The timeline is projected to be:

* **August 14, 2008: Django 1.0 beta release.** Past this point Django

  will be in a "feature freeze" for the 1.0 release; after Django 1.0

  beta, the development focus will be solely on bug fixes and

  stabilization.

* August 15, 2008: Sprint (based in Austin, Texas, USA, and online).

* August 17, 2008: Sprint (based in Tel Aviv, Israel, and online).

* **August 21, 2008: Django 1.0 release candidate 1.** At this point,

  all strings marked for translation within Django's codebase will be

  frozen, to provide contributors time to check and finalize all of

  Django's bundled translation files prior to the final 1.0 release.

* August 22, 2008: Sprint (based in Portland, Oregon, USA, and online).

* **August 26, 2008: Django 1.0 release candidate 2.**

* August 30, 2008: Sprint (based in London, England, UK, and online).

* **September 2, 2008: Django 1.0 final release.** The official Django

  1.0 release party will take place during the first-ever DjangoCon,

  to be held in Mountain View, California, USA, September 6-7.

Of course, like any estimated timeline, this is subject to change as

requirements dictate. The latest information will always be available

on the Django project wiki:

* https://code.djangoproject.com/wiki/VersionOneRoadmap

What you can do to help

=======================

In order to provide a high-quality 1.0 release, we need your

help. Although this alpha release is, again, *not* intended for

production use, you can help the Django team by trying out the alpha

codebase in a safe test environment and reporting any bugs or issues

you encounter. The Django ticket tracker is the central place to

search for open issues:

* https://code.djangoproject.com/timeline

Please open new tickets if no existing ticket corresponds to a problem

you're running into.

Additionally, discussion of Django development, including progress

toward the 1.0 release, takes place daily on the django-developers

mailing list:

* http://groups.google.com/group/django-developers

...and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If

you're interested in helping out with Django's development, feel free

to join the discussions there.

Django's online documentation also includes pointers on how to

contribute to Django:

* :doc:`contributing to Django </internals/contributing/index>`

Contributions on any level -- developing code, writing

documentation or simply triaging tickets and helping to test proposed

bugfixes -- are always welcome and appreciated.

===============================

Django 1.0 beta 2 release notes

===============================

Welcome to Django 1.0 beta 2!

This is the fourth in a series of preview/development releases leading

up to the eventual release of Django 1.0, currently scheduled to take

place in early September 2008. This releases is primarily targeted at

developers who are interested in testing the Django codebase and

helping to identify and resolve bugs prior to the final 1.0 release.

As such, this release is *not* intended for production use, and any

such use is discouraged.

What's new in Django 1.0 beta 2

===============================

Django's development trunk has been the site of nearly constant

activity over the past year, with several major new features landing

since the 0.96 release.  For features which were new as of Django 1.0

alpha 1, see :doc:`the 1.0 alpha 1 release notes

</releases/1.0-alpha-1>`. For features which were new as of Django 1.0

alpha 2, see :doc:`the 1.0 alpha 2 release notes

</releases/1.0-alpha-2>`. For features which were new as of Django 1.0

beta 1, see :doc:`the 1.0 beta 1 release notes </releases/1.0-beta>`.

This beta release includes two major features:

Refactored ``django.contrib.comments``

    As part of a Google Summer of Code project, Thejaswi Puthraya

    carried out a major rewrite and refactoring of Django's bundled

    comment system, greatly increasing its flexibility and customizability.

Refactored documentation

    Django's bundled and online documentation has also been

    significantly refactored; the new documentation system uses

    `Sphinx`_ to build the docs and handle such niceties as topical

    indexes, reference documentation and cross-references within the

    docs. You can check out the new documentation `online`_ or, if you

    have Sphinx installed, build the HTML yourself from the

    documentation files bundled with Django.

.. _Sphinx: http://sphinx-doc.org/

.. _online: https://docs.djangoproject.com/

Along with these new features, the Django team has also been hard at

work polishing Django's codebase for the final 1.0 release; this beta

release contains a large number of smaller improvements and bugfixes

from the ongoing push to 1.0.

Also, as part of its ongoing deprecation process, Django's old

form-handling system has been removed; this means ``django.oldforms``

no longer exists, and its various API hooks (such as automatic

manipulators) are no longer present in Django. This system has been

completely replaced by :doc:`the new form-handling system

</topics/forms/index>` in ``django.forms``.

The Django 1.0 roadmap

======================

One of the primary goals of this beta release is to focus attention on

the remaining features to be implemented for Django 1.0, and on the

bugs that need to be resolved before the final release. As of this

beta release, Django is in its final "feature freeze" for 1.0; feature

requests will be deferred to later releases, and the development

effort will be focused solely on bugfixing and stability. Django is

also now in a "string freeze"; translatable strings (labels, error

messages, etc.) in Django's codebase will not be changed prior to the

release, in order to allow our translators to produce the final 1.0

version of Django's translation files.

Following this release, we'll be conducting a final development sprint

on August 30, 2008, based in London and coordinated online; the goal

of this sprint will be to squash as many bugs as possible in

anticipation of the final 1.0 release, which is currently targeted for

**September 2, 2008**. The official Django 1.0 release party will take

place during the first-ever DjangoCon, to be held in Mountain View,

California, USA, September 6-7.

What you can do to help

=======================

In order to provide a high-quality 1.0 release, we need your

help. Although this beta release is, again, *not* intended for

production use, you can help the Django team by trying out the beta

codebase in a safe test environment and reporting any bugs or issues

you encounter. The Django ticket tracker is the central place to

search for open issues:

* https://code.djangoproject.com/timeline

Please open new tickets if no existing ticket corresponds to a problem

you're running into.

Additionally, discussion of Django development, including progress

toward the 1.0 release, takes place daily on the django-developers

mailing list:

* http://groups.google.com/group/django-developers

...and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If

you're interested in helping out with Django's development, feel free

to join the discussions there.

Django's online documentation also includes pointers on how to

contribute to Django:

* :doc:`contributing to Django </internals/contributing/index>`

Contributions on any level -- developing code, writing

documentation or simply triaging tickets and helping to test proposed

bugfixes -- are always welcome and appreciated.

===============================

Django 1.0 beta 1 release notes

===============================

Welcome to Django 1.0 beta 1!

This is the third in a series of preview/development releases leading

up to the eventual release of Django 1.0, currently scheduled to take

place in early September 2008. This releases is primarily targeted at

developers who are interested in testing the Django codebase and

helping to identify and resolve bugs prior to the final 1.0 release.

As such, this release is *not* intended for production use, and any

such use is discouraged.

What's new in Django 1.0 beta 1

===============================

Django's development trunk has been the site of nearly constant activity over

the past year, with several major new features landing since the 0.96 release.

For features which were new as of Django 1.0 alpha 1, see :doc:`the 1.0 alpha 1

release notes </releases/1.0-alpha-1>`. For features which were new as of Django

1.0 alpha 2, see :doc:`the 1.0 alpha 2 release notes </releases/1.0-alpha-2>`.

This beta release does not contain any major new features, but does

include several smaller updates and improvements to Django:

Generic relations in forms and admin

    Classes are now included in ``django.contrib.contenttypes`` which

    can be used to support generic relations in both the admin

    interface and in end-user forms. See :ref:`the documentation for

    generic relations <generic-relations>` for details.

Improved flexibility in the admin

    Following up on the refactoring of Django's administrative

    interface (``django.contrib.admin``), introduced in Django 1.0

    alpha 1, two new hooks have been added to allow customized pre-

    and post-save handling of model instances in the admin. Full

    details are in :doc:`the admin documentation </ref/contrib/admin/index>`.

``INSERT``/``UPDATE`` distinction

    Although Django's default behavior of having a model's ``save()``

    method automatically determine whether to perform an ``INSERT`` or

    an ``UPDATE`` at the SQL level is suitable for the majority of

    cases, there are occasional situations where forcing one or the

    other is useful. As a result, models can now support an additional

    parameter to ``save()`` which can force a specific

    operation. Consult the database API documentation for details

    and important notes about appropriate use of this parameter.

Split ``CacheMiddleware``

   Django's ``CacheMiddleware`` has been split into three classes:

   ``CacheMiddleware`` itself still exists and retains all of its

   previous functionality, but it is now built from two separate

   middleware classes which handle the two parts of caching (inserting

   into and reading from the cache) separately, offering additional

   flexibility for situations where combining these functions into a

   single middleware posed problems. Full details, including updated

   notes on appropriate use, are in

   :doc:`the caching documentation </topics/cache>`.

Removal of deprecated features

    A number of features and methods which had previously been marked

    as deprecated, and which were scheduled for removal prior to the

    1.0 release, are no longer present in Django. These include

    imports of the form library from ``django.newforms`` (now located

    simply at ``django.forms``), the ``form_for_model`` and

    ``form_for_instance`` helper functions (which have been replaced

    by ``ModelForm``) and a number of deprecated features which were

    replaced by the dispatcher, file-uploading and file-storage

    refactorings introduced in the Django 1.0 alpha releases. A full

    list of these and all other backwards-incompatible changes is

    available on `the Django wiki`_.

A number of other improvements and bugfixes have also been included:

some tricky cases involving case-sensitivity in differing MySQL

collations have been resolved, Windows packaging and installation has

been improved and the method by which Django generates unique session

identifiers has been made much more robust.

.. _the documentation for generic relations: ../contenttypes/#generic-relations

.. _the Django wiki: https://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#Removedseveralmoredeprecatedfeaturesfor1.0

The Django 1.0 roadmap

======================

One of the primary goals of this beta release is to focus attention on

the remaining features to be implemented for Django 1.0, and on the

bugs that need to be resolved before the final release. Following this

release, we'll be conducting a series of development sprints building

up to the release-candidate stage, followed soon after by Django

1.0. The timeline is projected to be:

* August 15, 2008: Sprint (based in Austin, Texas, USA, and online).

* August 17, 2008: Sprint (based in Tel Aviv, Israel, and online).

* **August 21, 2008: Django 1.0 release candidate 1.** At this point,

  all strings marked for translation within Django's codebase will be

  frozen, to provide contributors time to check and finalize all of

  Django's bundled translation files prior to the final 1.0 release.

* August 22, 2008: Sprint (based in Portland, Oregon, USA, and online).

* **August 26, 2008: Django 1.0 release candidate 2.**

* August 30, 2008: Sprint (based in London, England, UK, and online).

* **September 2, 2008: Django 1.0 final release.** The official Django

  1.0 release party will take place during the first-ever DjangoCon,

  to be held in Mountain View, California, USA, September 6-7.

Of course, like any estimated timeline, this is subject to change as

requirements dictate. The latest information will always be available

on the Django project wiki:

* https://code.djangoproject.com/wiki/VersionOneRoadmap

What you can do to help

=======================

In order to provide a high-quality 1.0 release, we need your

help. Although this beta release is, again, *not* intended for

production use, you can help the Django team by trying out the beta

codebase in a safe test environment and reporting any bugs or issues

you encounter. The Django ticket tracker is the central place to

search for open issues:

* https://code.djangoproject.com/timeline

Please open new tickets if no existing ticket corresponds to a problem

you're running into.

Additionally, discussion of Django development, including progress

toward the 1.0 release, takes place daily on the django-developers

mailing list:

* http://groups.google.com/group/django-developers

...and in the ``#django-dev`` IRC channel on ``irc.freenode.net``. If

you're interested in helping out with Django's development, feel free

to join the discussions there.

Django's online documentation also includes pointers on how to

contribute to Django:

* :doc:`contributing to Django </internals/contributing/index>`

Contributions on any level -- developing code, writing

documentation or simply triaging tickets and helping to test proposed

bugfixes -- are always welcome and appreciated.