Code Release follows the General Code Release Timeline process
General Code Release Timeline
| Event | When (time before release) | What happens |
|---|---|---|
| science freeze for simulations | 24 months before | All PRs for features intended to be released and used in associated simulations posted on github. Must be complete and ready to integrate. After integrations are complete, start component-level, "standalone" tuning. |
| Component tuning completed | 19 months before | All component level tuning must be done. Atmosphere-only cases, ocean-only, land-only, etc. All input files finished. |
| Coupled runs begin | 18 months before | Coupled simulations begin. |
| All science freee | 1 month before | Any science code changes to be in release must have their PR merged to master by this date. Non-science config/performance changes still allowed. |
| Code Freeze | 1 week before | No changes to any executed code. May still update README's and other documentation. Conduct final tests. Get DOI |
| vX.Y.0 tag made on master. | The release | New climate-changing PRs can be merged to master after this. Maintenance branch for release made. |
| Announce | days to few weeks after release | Send emails, update e3sm.org |