Code


Version 52 (modified by orzel, 23 months ago) (diff)

Not needed anymore since the move out of svn.

Branches

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 http://docs.djangoproject.com/en/dev/internals/contributing/#branch-policy 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.

Bazaar

Launchpad mirrors Django's trunk: https://launchpad.net/django

You can fetch it with:

bzr branch lp:django

Git

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

Mercurial (hg)

Other repositories

  • 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.