Development/Beta Cycle

From MusicBrainz Wiki
< Development
Revision as of 13:52, 10 June 2012 by 195.24.233.122 (talk) (6. Are there any open tickets for beta.mb (check 'Fix version==beta'))

1. Write code

2. Does code need reviewing?

  • Yes: Create code review. Change ticket status to "In 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. Change ticket status to "In Beta Testing".
  • No: Figure out how to handle schema changes and the like.

6. Are there any open tickets for beta.mb (check 'Fix version==beta')?

  • Yes: Remove the broken branches from beta and reopen the ticket. Change ticket status to "In Progress". 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.