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

Current as of Dec 12, 2010.

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

*: Bug fixes to new features or Very Important new features _might_ go into *V7_5_5-branch*, but only with permission of the wrangler.  If so, they should then be merged into *master*.

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

{strike}
*: Very Important bug fixes should go into *V7_4_3-branch*, but only with permission of the wrangler. If so, they should then be merged into *V7_4-branch*, and from there into *master*.
{endstrike}

*: Recently abandoned branches that should not receive new code: V7_4_2-branch, V7_2-branch, V7_3-branch, V7_3_2-branch.

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

Current as of Oct 15, 2010.

*: Right now, the *master* branch is for 7.5.5 documentation.

*: The *V7_5_4-branch* is for 7.5.4 documentation, as well as items relevant to 7.5.< 3 |2 | 1 | 0 > that never got put into the manual.

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

*: The *V7_4_4-branch* is for all documentation related to 7.4.<4 | 3 | 2 | 1 | 0> (in general).

When in doubt, ask Karen.

{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}