• tl;dr
• Introduction
• Overview
• Tests
• Using git
• Getting a code review
• Why
• When
• Who
• How
• What (to do when the patch is abandoned)
• Landing a patch
• Squashing commits
• Regressions in functionality
• Regressions in performance
• Performance regressions caused by auto-roller commits
• Avoid "Revert "Revert "Revert "Revert "Fix foo"""" commit messages
• Landing Revert Changes
• Handling breaking changes
• 1. Determine if your change is a breaking change
• 2. Evaluate the breaking change proposal
• 3. Prepare your change.
• 4. Land your change.
• 5. Document the change, including clear documentation for migrating code, with samples, and clear rationales for each change
• Deprecations
• Skipped Tests