Django-celery

=====
:release-date: 2011-08-05 12:00 PM BST

* Now depends on Celery 2.3.0

Please read the Celery 2.3.0 changelog!

.. _version-2.2.4:

=====

* celerybeat: DatabaseScheduler would not react to changes when using MySQL and
the default transaction isolation level ``REPEATABLE-READ`` (Issue 41).

It is still recommended that you use isolation level ``READ-COMMITTED``
(see the Celery FAQ).

.. _version-2.2.3:

=====
:release-date: 2011-02-12 16:00 PM CET

* celerybeat: DatabaseScheduler did not respect the disabled setting after restart.

* celeryevcam: Expiring objects now works on PostgreSQL.

* Now requires Celery 2.2.3

.. _version-2.2.2:

=====
:release-date: 2011-02-03 16:00 PM CET

* Now requires Celery 2.2.2

* Periodic Task Admin broke if the CELERYBEAT_SCHEDULE setting was not set.

* DatabaseScheduler No longer creates duplicate interval models.

* The djcelery admin templates were not included in the distribution.

.. _version-2.2.1:

=====

:release-date: 2011-02-02 16:00 PM CET

* Should now work with Django versions previous to 1.2.

.. _version-2.2.0:

=====
:release-date: 2011-02-01 10:00 AM CET

* Now depends on Celery v2.2.0

* djceleryadm: Adds task actions Kill and Terminate task

* celerycam: Django's queryset.delete() fetches everything in
memory THEN deletes, so we need to use raw SQL to expire objects.

* djcelerymon: Added Command.stdout + Command.stderr (Issue 23).

* Need to close any open database connection after any embedded
celerybeat process forks.

* Added contrib/requirements/py25.txt

* Demoproject now does ``djcelery.setup_loader`` in settings.py.

.. _version-2.1.1: