Code

Changes between Version 2 and Version 3 of DjangoBranches


Ignore:
Timestamp:
09/26/07 06:40:54 (7 years ago)
Author:
korpios
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DjangoBranches

    v2 v3  
    2727We 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'' [http://en.wikipedia.org/wiki/Revision_control 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 [http://bazaar-vcs.org/ Bazaar], [http://git.or.cz/ Git], [http://www.selenic.com/mercurial/ Mercurial], and [http://svk.bestpractical.com/ SVK]. 
    2828 
    29 Tom Tobin has set up a Mercurial repository mirroring Django's trunk at [http://hg.korpios.com/django.trunk]. 
     29Tom Tobin has set up a couple of distributed repositories mirroring Django: 
     30 
     31 * Git: `git://git.korpios.com/django.git` 
     32 * Mercurial: `http://hg.korpios.com/django.trunk` 
    3033 
    3134Please note that the information regarding branches in the [http://www.djangoproject.com/documentation/contributing/#branch-policy Contributing] document is out of date with regards to Django's branch creation policy.