Version 38 (modified by trbs, 6 years ago) (diff)

new users should use the bitbucket mirror repositories not mine


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

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)

  • Bitbucket: The Bitbucket crew maintains a number of Mercurial repositories that track official repositories of different projects, all of them owned by the mirror pseudo user. In particular there are a Django trunk and Django 1.0.x mirrors, both always up to date. (Note: the django-all mirror seems to be the most correctly implemented since it tracks branches and tags properly)
  • GeoDjango Mercurial: includes gis-newforms (a merge of the gis and newforms-admin branches), example code, and other geospatial goodies.
  • DjangoBugfixes: An experimental MQ repository following the trunk branch of Django. More info is available here.
Back to Top