The Big Picture of E3SM Model Development (for E3SM staff)
All E3SM developers should be familiar with the basics of development with git including cloning the E3SM repo, making a branch, committing changes and submitting a Pull Request on Github. Also writing good commit messages and pull request descriptions. Read the Development Getting Started Guide and Commit and PR message template. For more info see, the Git Tutorial and Development Reference.
Group Leads and Epic leads coordinate and schedule development relevant to their group and/or epic. They should have developers assigned to work on features in the order necessary to meet deliverables in the Roadmaps (the leads might also be the developers). Epic leads should make sure developers are finishing their work and getting it merged to the E3SM "master" branch.
Mailing Lists: Note that getting a confluence account does not automatically add you to the relevant mailing lists. All users should periodically review the list of mailing lists and join any that may be relevant: Email Lists/wiki/spaces/ED/pages/818381294
Integrators: every group has 2 or 3 Integrators who take completed feature branches and, if they meet the requirements, merge them to master. See Integrator Guide for more info.
The Water Cycle Coupled Model Group establishes the timeline for integrating new features for the new release, relevant testing criteria, and when the master should be tagged (using the Branch, Tag, and Version name conventions) all timed to meet E3SM deliverables as defined in the Roadmaps. Integrators should be aware of the Roadmap for their component.
...