Development/Beta Cycle: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
* If possible, use test.musicbrainz.org |
* If possible, use test.musicbrainz.org |
||
* If not possible (ie, there are schema changes) use an mbsandbox |
* If not possible (ie, there are schema changes) use an mbsandbox |
||
=== 3. Does code need reviewing? === |
=== 3. Does code need reviewing? === |
||
* Yes: Continue. |
* Yes: Continue. |
||
| Line 13: | Line 12: | ||
* Yes: Wait. Go back to step 5. |
* Yes: Wait. Go back to step 5. |
||
* No: Continue. |
* No: Continue. |
||
=== 6. |
=== 6. Is this a change that can go live immediately? === |
||
=== 7. Is this a change that can go live immediately? === |
|||
* Yes: Continue. |
* Yes: Continue. |
||
* No: Figure out how to handle schema changes and the like. |
* No: Figure out how to handle schema changes and the like. |
||
=== |
=== 7. Ship code to beta === |
||
=== |
=== 8. Are there any open tickets for beta.mb? === |
||
* Yes: Remove the broken branches from beta and reopen the ticket. Go back to step 3. |
* Yes: Remove the broken branches from beta and reopen the ticket. Go back to step 3. |
||
* No: Continue. |
* No: Continue. |
||
| ⚫ | |||
| ⚫ | |||
* Yes: Merge current beta testing branches to master (these will have no open bugs). Merge master to production. Reset beta and next to master. Release |
* Yes: Merge current beta testing branches to master (these will have no open bugs). Merge master to production. Reset beta and next to master. Release |
||
* No: Go fix something else. |
* No: Go fix something else. |
||
Revision as of 13:37, 10 June 2012
1. Write code
2. Put code on non-live test server
- If possible, use test.musicbrainz.org
- If not possible (ie, there are schema changes) use an mbsandbox
3. Does code need reviewing?
- Yes: Continue.
- No: Go to step 6.
4. Has code passed code review?
- Yes: Continue.
- No: Fix bugs. Go back to step 4.
5. Is next release < 7 days?
- Yes: Wait. Go back to step 5.
- No: Continue.
6. Is this a change that can go live immediately?
- Yes: Continue.
- No: Figure out how to handle schema changes and the like.
7. Ship code to beta
8. Are there any open tickets for beta.mb?
- Yes: Remove the broken branches from beta and reopen the ticket. Go back to step 3.
- No: Continue.
9. Is it time to release?
- Yes: Merge current beta testing branches to master (these will have no open bugs). Merge master to production. Reset beta and next to master. Release
- No: Go fix something else.
