Version 21 (modified by 16 years ago) ( diff ) | ,
---|
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!
Active Branches
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.
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.
- 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/
- The django changes are sporadically published on repo.or.cz: http://repo.or.cz/w/django.git/
- Jacob Kaplan-Moss has also set up an experimental git mirror (django-developers post):
- Repository: git://djangoproject.com/django (browse)
- Other people also published their repositories, in case you want to add them as remotes:
Mercurial (hg)
- [Preferred] Full Mercurial mirror hosted at dpaste.com, updated every fifteen minutes: 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 thegis
andnewforms-admin
branches), example code, and other geospatial goodies.