Version 33 (modified by Alex Gaynor, 10 years ago) (diff)



Development of major new features for Django tends to take place in branches — copies of the main codebase focused on a particular feature. Using branches makes it easier to experiment with such sweeping changes without possibly breaking the trunk — the main line of development.

Branches may not be stable, but they offer a chance to test out bleeding-edge code before it hits the mainline. Give them a try, and remember to send feedback to the branch maintainers!

  1. Active Branches
  2. Creating New Branches
  3. DVCS mirrors

Active Branches

  • Django Aggregates, as a part of the 2008 Google Summer of Code project work was done on adding aggregate support to the Django ORM, this is currently under active development

Creating New Branches

Please see for information about creating new feature branches.

DVCS mirrors

If you have a branch of Django maintained with a DVCS tool, please add it below.


Launchpad mirrors Django's trunk:

You can fetch it with:

bzr branch lp:django


There are several git repositories out there, some of which are used to develop patches that will come to SVN.

Mercurial (hg)

Back to Top