*: Code that implements new features or non-urgent bug fixes, aka code targeted for v8.7, should go into the *master* branch. -*: Urgent bug fixes to the development series release candidate may go into *V8_7_4-branch, but only with permission of the wrangler*. They should then be merged into *master*. {linebreak} {strike}V8_7_4-branch is *frozen* with the exception of documentation commits, and requests to commit to this branch will probably be denied.{endstrike} +*: Urgent bug fixes to the development series release candidate may go into *V8_7_4-branch, but only with permission of the wrangler*. They should then be merged into *master*. {linebreak} V8_7_4-branch is *frozen* with the exception of documentation commits, and requests to commit to this branch will probably be denied. -*: Serious bug fixes to stable series go into the *V8_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 -*:: *V8_7_4-branch* +_ALL COMMITS TO A STABLE BRANCH {wiki: PerformingCodeReviews MUST BE CODE REVIEWED}_ - the ticket should show who did the code review. + +*: Urgent bug fixes to the stable series release candidate may go into the *V8_6_7-branch, but only with permission of the wrangler*. {linebreak}*V8_6_7-branch* is *frozen* with the exception of documentation commits, and requests to commit to this branch will probably be denied. Approved changes should then be merged into +*:: *V8_7_4-branch *:: *master*, as above. +{linebreak}(We _bypass_ the *V8_6-branch* whenever there is an active development series release branch.) + + +*: Less serious bug fixes to stable series go into the *V8_6-branch* Commits should then be merged into *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. +*: If code needs to be reviewed before pushing, then can 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. {section: List of all source code branches}