= 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!

[[PageOutline(2,, inline)]]

== Active Branches ==

 * Current there are six active branches, one for each student working as a part of the Google summer of code, they are located at: http://code.djangoproject.com/browser/django/branches/soc2009/

== 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 ===

[https://launchpad.net/ 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.

 * Jannis Leidel has set up a git mirror on github, updated every 30 minutes.
   * Repository: http://github.com/django/django/tree/master
 * Jacob Kaplan-Moss has also set up an experimental git mirror ([http://groups.google.com/group/django-developers/browse_thread/thread/7c96cbb1a13aa368 django-developers post]):
   * Repository: git://djangoproject.com/django [http://code.djangoproject.com/git/?p=django (browse)] (broken as for 2009-03-11)
 * Matthias Kestenholz has set up several git repositories for Django and for a selection of Django applications:
   * Gitweb with complete list of repositories: http://spinlock.ch/pub/git/ (broken as for 2009-03-11, http protocol works fine as of 2009-03-18, git protocol is stil broken)
   * The django changes are sporadically published on repo.or.cz: http://repo.or.cz/w/django.git/ (as for 2009-03-11, last update is 5 months old)
 * Other people also published their repositories, in case you want to add them as remotes:
   * brosner: git://github.com/brosner/django.git [http://github.com/brosner/django/tree/master (browse)]
   * Marc Fargas (telenieko): git://www.marcfargas.com/django.git/ [http://www.marcfargas.com/gitweb/?p=django.git;a=summary (browse)]
   * Alex Gaynor: http://github.com/alex/django/tree/master

=== 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 [http://bitbucket.org/mirror/ mirror] pseudo user. In particular there are a [http://bitbucket.org/mirror/django-trunk/ Django trunk] and [http://bitbucket.org/mirror/django-10x/ Django 1.0.x] mirrors, both always up to date. (Note: the [http://bitbucket.org/mirror/django-all/ django-all] mirror seems to be the most correctly implemented since it tracks branches and tags properly)
 * SVN2HG Gateway of Django and Active branches, updated hourly: [http://hgsvn.trbs.net/django/]
 * [http://geodjango.org/hg/ GeoDjango Mercurial]: includes `gis-newforms` (a merge of the `gis` and `newforms-admin` branches), example code, and other geospatial goodies.
 * [http://joelia.gthc.org/django-bugfixes/ DjangoBugfixes]: An experimental MQ repository following the trunk branch of Django. More info is available [http://gthc.org/wiki/PythonWebDevelopment/DjangoBugfixes here].