Skip to content

Conversation

@TomasTorsvik
Copy link
Contributor

PR for 3.0.beta10

Each tag should preferably only include major updates from one component (e.g. include large code
changes from upstream repositories, large structural changes, new (default) model capability).
Minor component updates can be included in addition, if they do not change model output substantially.

Main objective: (TBD)

CCS_CONFIG:
Point to new input data location (create issue on this, WP8 work on this)

OLIVIA settings

  • Run DEBUG mode out-of-the-box (ccs_config?)

CAM:

  • CO2 update (ready to go)
  • Nudging update (needs more work)
  • missing emission files for CMIP7 (Dirk working on this)

Components:

Checkmarked components are already latest version, and will not be updated in this tag.
If a component needs an update, remove checkmark and edit tag name to the new one that will be used.
If appropriate, also include link to resolved issues/PRs as sub-list under the relevant component.

  • BLOM: v1.12.23
  • CAM: noresm3_0_021_cam6_4_121
  • CTSM: ctsm5.3.045_noresm_v14
  • ccs_config: ccs_config_noresm0.0.54
  • CICE: noresm_cice6_6_1_20251129_v1
  • CISM: cismwrap_2_2_007_noresm_v0
  • CTSM: ctsm5.4.002_noresm_v1
  • MOSART: mosart1.1.12_noresm_v0
  • WW3: ww3_interface_noresm0.0.18
  • CISM: cismwrap_2_2_007_noresm_v0
  • CMEPS: cmeps1.0.39_noresm_v10
  • CDEPS: cdeps1.0.70_noresm_v7

Coupled development

Bugs / bug fixes

Test procedure for new tags

@TomasTorsvik TomasTorsvik added this to the noresm3_0_beta10 milestone Dec 23, 2025
@TomasTorsvik TomasTorsvik added the code release Issues related to upcoming code release or tagging label Dec 23, 2025
@TomasTorsvik TomasTorsvik mentioned this pull request Dec 23, 2025
12 tasks
@TomasTorsvik TomasTorsvik linked an issue Dec 23, 2025 that may be closed by this pull request
12 tasks
@TomasTorsvik
Copy link
Contributor Author

@mvertens , @mvdebolskiy , @gold2718 , @matsbn , @monsieuralok
As discussed earlier with @mvertens, we would like to change the procedure for merging into the noresm_develop branch. Instead of merging from personal forks, we make a feature branch in the main repository and open a draft PR. The idea is that it should be easier for everyone to follow what is happening in the development branch, and have a common place to discuss development towards a tag.

At the same time, I have closed the issue #752 for noresm3_0_beta10, and opened a new issue #755 for noresm3_0_beta11. Issues for later tags may be added as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

code release Issues related to upcoming code release or tagging

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

noresm3_0_beta10

2 participants