|Version 23 (modified by pbx, 5 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!
There are no active branches at this time.
Creating New Branches
Please see http://docs.djangoproject.com/en/dev/internals/contributing/#branch-policy for information about creating new feature branches.
If you have a branch of Django maintained with a DVCS tool, please add it below.
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.
- Jacob Kaplan-Moss has also set up an experimental git mirror (django-developers post):
- Matthias Kestenholz has set up several git repositories for Django and for a selection of Django applications:
- Other people also published their repositories, in case you want to add them as remotes:
- [Preferred] Mercurial mirror of trunk, updated hourly: http://hg.dpaste.com/django/
- SVN2HG Gateway of Django and Active branches, updated hourly: http://hgsvn.trbs.net/django/
- GeoDjango Mercurial: includes gis-newforms (a merge of the gis and newforms-admin branches), example code, and other geospatial goodies.