Development/Beta Cycle: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
* Yes: Create code review. Put on a non-live test server. |
* Yes: Create code review. Put on a non-live test server. |
||
** Usually test.musicbrainz.org, a mbsandbox in the case of complicated schema changes. Await juicy shipits. |
** Usually test.musicbrainz.org, a mbsandbox in the case of complicated schema changes. Await juicy shipits. |
||
* No: Go to step |
* No: Go to step 4. |
||
=== 3. Has code passed code review? === |
=== 3. Has code passed code review? === |
||
* Yes: Continue. |
* Yes: Continue. |
||
Revision as of 13:43, 10 June 2012
1. Write code
2. Does code need reviewing?
- Yes: Create code review. Put on a non-live test server.
- Usually test.musicbrainz.org, a mbsandbox in the case of complicated schema changes. Await juicy shipits.
- No: Go to step 4.
3. Has code passed code review?
- Yes: Continue.
- No: Fix bugs. Go back to step 1.
4. Is next release < 7 days?
- Yes: Wait until there are >= 7 days.
- No: Continue.
5. Is this a change that can go live immediately?
- Yes: Merge to beta.
- No: Figure out how to handle schema changes and the like.
6. Are there any open tickets for beta.mb?
- Yes: Remove the broken branches from beta and reopen the ticket. Go back to step 1.
- No: Continue.
7. Is it time to release?
- Yes: Merge current individual 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.
