Source Code Branches

Not logged in

• Browse
• Help
• Home
• Login
• Reports
• Search
• Timeline
• Wiki

• Contents
• No-Diff
• Text

 {section: Active source code release branches, or where should my code go?}
 
-Current as of September 15, 2011.
+Current as of October 13th, 2011.
 
 *: 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_2-branch*, but only with permission from the wrangler.  They should then be merged into *master*.
+{strike}*: Urgent bug fixes to new features might go into *V7_7_3-branch*, but only with permission from the wrangler, and after that branch is created.  They should then be merged into *master*.{endstrike}
 
-*: 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_2* and thence to *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*.
 
 {strike}
 *: Very Very Urgent bug fixes to old features might go into *V7_6_4-branch*, but only with permission from the wrangler.

This work is supported by NSF under Cooperative Agreement OAC-2030508 as part of the PATh Project. Any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF. Site built using CVSTrac.