User:Bitmap/Beta Cycle
From MusicBrainz Wiki
Jump to navigationJump to search
Note: This process does not apply to patches that require schema changes, or that need to be hot-fixed.
1. Write code.
2. Does the code need reviewing?
- Yes: Continue.
- No: Go to step 5.
3. Submit code for review.
- Change ticket status to "In Review".
4. Has the code passed code review?
- Yes: Continue.
- No: Fix bugs. Go back to step 1.
5. Merge code to master.
6. Is the code fixing an issue not affecting the production branch?
- Yes: Go to step 8.
- No: Continue.
7. Is the next release more than 7 days away?
- Yes: Continue.
- No: Go to step 10.
8. Merge code to beta.
9. Is the code fixing an issue not affecting the production branch?
- Yes: Close ticket as "Fixed".
- No: Change ticket status to "In Beta Testing".
10. Is it time to release?
- Yes: Continue.
- No: Stop. Go fix something else.
11. Merge beta into production.
- Tag the release from the production branch.