{section: Active source code release branches, or where should my code go?}
-Current as of Sept 16, 2009.
+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 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_4-branch, and master. Once we release v7.4.0, we can abandon the V7_2-branch.
+*: High priority bugs fixes for problems introduced since 7.2 should land on *V7_4_0-branch*. _Almost no bugs meet this standard._ double check with AlanDeSmet if you're not sure. 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?}
