Version 20 (modified by simon, 10 years ago) (diff)

No active branches at this time


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. Distributed version control mirrors

Active Branches

There are no active branches at this time.

Creating New Branches

We are discouraging the creation of new branches inside Django's subversion repository. If you'd like to work on a major new contribution to Django, we encourage you to set up a new "branch" elsewhere and let the Django-developers mailing list know about it. One tactic is to use a distributed revision control system ("DRCS", or sometimes "DSCM", see Wikipedia's article on revision control); these systems allow you to create your own repository anywhere you'd like, and typically include tools to import from Subversion. Options here include Bazaar, Git, Mercurial, and SVK.

Please note that the information regarding branches in the Contributing document is out of date with regards to Django's branch creation policy.

Distributed version control mirrors


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