Some weeks ago, Django get his own clear release process : http://docs.djangoproject.com/en/dev/internals/release-process/

I have proposed rules for our team to create Django-projects:

• We develop using current stable version (1.0, 1.1 or 1.1.4)
• If security Django release appears (e.g. 1.0.3) every project immediately moves to this release
• If our project should be released after new “big” Django release or just before (1-2 weeks) , separate branch should be created and project should be tested vs Django beta. After final release, this separate branch becomes master.
• For special cases, e.g. project is long-tem and cover Django 1.0 and 2.0, which will be incompatible, policy should be discussed additionally.

Now we are using 1.0.X trunk, http://code.djangoproject.com/svn/django/branches/releases/1.0.X/

Do you agree? What policy do you use?