HTCondorWiki: Source Code Branches

 
 Current as of June 14, 2011.
 
-*: Commits intended for 7.6.2 of Condor should go into the *V7_6_2-branch* and then be merged into *V7_6-branch*, and then into *V7_7_0-branch*, and then into *master*. _ALL COMMITS TO THE V7_6_2-branch BRANCH MUST BE CODE REVIEWED AND COORDINATED WITH THE WRANGLER_
+*: Commits intended for 7.6.2 of Condor should go into the *V7_6_2-branch* and then be merged into *V7_6-branch*, and then into *master*. _ALL COMMITS TO THE V7_6_2-branch BRANCH MUST BE CODE REVIEWED AND COORDINATED WITH THE WRANGLER_
 
 *: Code that implements new features or non-urgent bug fixes, aka code targeted for v7.7.x, should go into branch *master*.
 
 *: Urgent bug fixes to new features might go into *V7_7_0-branch*, but only with permission from the wrangler.  They should then be merged into *master*.
 
-*: Serious bug fixes to stable series features should go into *V7_6-branch*. _ALL COMMITS TO A STABLE BRANCH {wiki: PerformingCodeReviews MUST BE CODE REVIEWED}_ - the ticket should show who did the code review. Commits should then be merged into *V7_7_0-branch* and then into *master*.
+*: Serious bug fixes to stable series features should go into *V7_6-branch*. _ALL COMMITS TO A STABLE BRANCH {wiki: PerformingCodeReviews MUST BE CODE REVIEWED}_ - the ticket should show who did the code review. Commits should then be merged into *master*.