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

Current as of Oct 13, 2009.

*: Code that implements new features, aka code targeted for v7.5.x, should go into branch *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_4-branch, and master.  Once we release v7.4.0, we can abandon the V7_2-branch.

*: Fixes for #422, #714, and #790 land on *V7_4_0-branch*.  Only showstoppers can be added to this list, and must be run by AlanDeSmet.  Once landed, merge to V7_4-branch, then master.

*: Other bug fixes should go into branch *V7_4-branch* (which will eventually be 7.4.1), and be merged into master.

*: Note: The *V7_3_2-branch* release branch is now abandoned, as v7.3.2 has been released to the web on 9/16/09.

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

Current as of Oct 22, 2009.

*: Right now, the *master* branch is for 7.5 series and 7.5.0 documentation.

*: The *V7_4-branch* is for all documentation new to 7.4.1.

*: The *V7_4_0-branch* is for all documentation related to 7.4.0, and 7.4.x (in general).

{section: List of all source code branches}

Below is a table of all branches in our repository and when/who last did a commit to them.  {wiki: GitBranchDescriptions Documentation} about what each branch is about is also available.

{report: 13}