Bug Review Process

Bug is reported (by core dev or external user)
Bug is triaged (during weekly meeting, if not earlier)
- assigned lead developer
- assigned target release
Assigned developer fully assess work and manages estimates for:
- timing and difficulty
- target release
- risk profile and testing requirements
Assigned developer implements fix
- code is checked in to current hot fix branch
Assigned developer reassigns issue to a reviewer and marks it as “Review”
Reviewer checks code and reassigns to original developer
- if good: then mark as “Closed"
- if more work needed: then mark as “Open”. Repeat fix and review steps
As part of release planning:
- coordinate testing
- cherry pick code into trunk

Cherry picking

git checkout FIX-BRANCH
git cherry-pick -x DEV-COMMIT-HASH-CODE