{section: Active source code release branches, or where should my code go?}

*: Code that implements new features, aka code targeted for v7.5.x, should go into branch *master*.

*: Code that fixes bugs introduced in the v7.3.x series, and therefore is targeted for v7.4.x, should go into branch *V7_4-branch*, and be merged into master.

*: Code that fixes _serious_ bugs that existed in v7.2.x should go into branch *V7_2-branch*, and be merged into branches V7_3_2-branch, V7_4-branch, and master.  Once we release v7.4.0, we can abandon the V7_2-branch.

*: Code that must go into v7.3.2 should go into the *V7_3_2-branch* release branch and then merged into V7_4-branch and master.  _However, you had better get permission from the wranger_, and v7.3.2 is now frozen.


{section: Active doc branches, or where should my documentation go?}

Current as of Sept 10, 2009.

*: Right now, the *master* branch is for 7.4 series and 7.4.0 documentation.

*: The *V7_3_2-branch*  is for all documentation improvements as well as 7.3.2 documentation.

*: Right now,  there is no place for 7.5 series documentation.  Talk to Karen, if you need the proper documentation branches made.

{section: List of all source code branches}

{report: 13}