Milestones
List view
- Due by November 30, 2026•6/18 issues closed
Freeze of FATES version in CTSM5.4 until ctsm6.0.000 FATES changes will go onto fates-dev during this period The FATES maint-version branch may be updated with required bug-fixes during this period Documentation on the process: https://docs.google.com/document/d/1LOxCUZXWPjDGldrd2aJmsGjIVjKOS8-oBBvG5nk_ElU/edit?tab=t.0
Overdue by 3 day(s)•Due by October 30, 2026•13/16 issues closedThis hasn't been prioritized yet, but this is something that we think really should happen. In order for it to really happen it needs to be moved into a tangible milestone. So putting it here means it's probably longer timescale than the existing milestones. As it isn't a more immediate priority, or we don't have the bandwidth to handle it, but we do think it's important to do at least long term. In many cases it's something we'd like to do NOW, but know it's not important enough to do immediately in order to get the true near term priorities done. In Scrum Agile Software Development Methodology (SDM) terminology this is something in the "Backlog".
Due by December 31, 2040•10/95 issues closedPost cesm3.0 science and software developments into the CESM release series. Things that we want to see in the ctsm7.0.000 tag and release-clm7.0 tag on main. Which will be the starting point for the CESM4.0.0 release branch. This will be marked as a release.
Due by December 12, 2030•3/68 issues closedPost cesm3.0/ctsm6.0.0 developments. - New physics version that will change answers for development (call it clm6_5 physics? with Clm65 in the compset names?) - Change defaults for clm6_5 physics with new developments as they come in: - Turn new A/C humidty on by default for clm6_5 - Update historical compsets with a new physics version that includes updated aerosol and ndep Things that we want to see in the ctsm6.1.000 tag and release-clm6.1 tag on main. This will be marked as a release.
Due by June 11, 2027•7/85 issues closedNote this milestone shoud likely be split in two: 1) Compsets we need in place to do production runs & 2) Documentation, usability, etc that can take place after the release simulations are done Previously description was: Things that we want to see in the ctsm6.0.000 tag and release-clm6.0 tag on main. This will be marked as a release.
Due by December 18, 2026•203/485 issues closed