{section: Active source code release branches, or where should my code go?}

*: Code that implements new features or non-urgent bug fixes, aka code targeted for v8.7, should go into the *master* branch.

*: {strike}Urgent bug fixes to the development series release candidate may go into *V8_7_8-branch, but only with permission of the wrangler*. They should then be merged into *master*. {linebreak} V8_7_7-branch is *frozen* with the exception of documentation commits, and requests to commit to this branch will probably be denied.{endstrike}

_ALL COMMITS TO A STABLE BRANCH {wiki: PerformingCodeReviews MUST BE CODE REVIEWED}_ - the ticket should show who did the code review.

*: {strike}Urgent bug fixes to the stable series release candidate may go into the *V8_6_11-branch*, *but only with permission of the wrangler*. {linebreak} The *V8_6_11-branch* is *frozen* with the exception of documentation commits, and requests to commit to this branch will probably be denied. The wrangler or release manager will perform merges from release branches to
*:: *V8_7_8-branch
*:: *master*, as above.
{linebreak}(We _bypass_ the *V8_6-branch* whenever there is an active development series release branch.){endstrike}

*: 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 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}

Below is a table of all branches in our repository and when/who last did a commit to them.  {wiki: GitBranchDescriptions Documentation} about what each branch is about is also available.

{report: 13}