Source Code Branches

Not logged in

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

• Contents
• No-Diff
• Text

 
 *: Code that implements new features or non-urgent bug fixes, aka code targeted for v8.1.1, should go into branch *master*.
 
-*:Urgent bug fixes to developer release candidate go into *V8_1_0-branch, but only with permission of the wrangler*. They should then be merged into *master*. V8_1_0-branch is frozen, and requests to commit to this branch will probably be denied.
+*:Urgent bug fixes to developer release candidate go into *V8_1_0-branch, but only with permission of the wrangler*. They should then be merged into *master*.{linebreak} V8_1_0-branch is *frozen*, and requests to commit to this branch will probably be denied.
 
-*: Serious bug fixes to stable series features should go into *V8_0-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 {strike}*V8_1_0-branch* with permission of the wranger,and/or{endstrike}  *master*, as above.
+*: Serious bug fixes to stable series features should go into *V8_0-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
+*:: {strike}*V8_1_0-branch* with permission of the wranger,and/or{endstrike}
+*:: *master*, as above.
 
 *: If code needs to be reviewed before pushing, then you should use "git format-patch" to create a patch, and attach it to the ticket. If it's a larger change, you should put it into a topic branch instead.
 

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.