{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.1.2, should go into branch *master*.

*:Urgent bug fixes to developer release candidate go into *V8_1_1-branch, but only with permission of the wrangler*. They should then be merged into *master*. V8_1_1-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_1-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.

*: Very Very Urgent bug fixes to the release candidate might go into *V8_0_3-branch*, but only with permission from the wrangler, and merge from there into *V8_0-branch*, following rules above.

{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}