SOP: develop --> main

[joeflack4]

Overview

Trish:

Also, with OMIM having a develop branch, do you want to sort out when changes get pushed to main in the omim repo? That repo is less complicated than mondo-ingest, so no need for anything complicated just some process so we know when changes go into main that will effect a data release from the omim repo.

I'm thinking:

When to merge

• a. If something that will have an effect on outputs is merged into develop, we can / should immediately merge into main.
• b. Otherwise, this process only needs to be done so often; perhaps 1x/week before release, or maybe we can go based on a reminder of 1x/mon.

How to merge

1. Make a PR from develop to main
2. Joe can self-review that and only call in other reviewers if necessary.

• Joe can decide whether or not to run a build before merging and examine the outputs.
  • The easiest way is to make a release off of develop. If there's anything wrong with it, it can be deleted.

[joeflack4]

@twhetzel This is dead simple, what do you think?

[joeflack4]

• Decide on the SOP
• Put it in an existing or new Google Doc
  • @twhetzel Do you think we have an existing doc that's good for this kind of SOP? The same question also applies to these; maybe they should all go into the same doc:
    • SOP for feature branch development workflow mondo-ingest#405
    • SOP: Source repos & builds mondo-ingest#675
    • Docs / SOP: How to review a data build mondo-ingest#544