Changes between Version 55 and Version 56 of DjangoBranches


Ignore:
Timestamp:
Nov 30, 2013, 4:42:48 AM (10 years ago)
Author:
anonymous
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • DjangoBranches

    v55 v56  
    11= Branches =
    22
    3 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 ''master'' — the main line of development.[[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image([[Image(www.baidu.com)]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]])]]
     3Development 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 ''master'' — the main line of development.
    44
    55Branches 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!
Back to Top