Skip to content

No labels!

There aren’t any labels for this repository quite yet.

bfb
bfb
bit-for-bit
blocked: answer changing
blocked: answer changing
Can't be resolved until we're ready for answer changes on master
blocked: dependency
blocked: dependency
Wait to work on this until dependency is resolved
blocker
blocker
another issue/PR depends on this one
branch tag: release
branch tag: release
Changes go on release branch as well as master
bug
bug
something is working incorrectly
closed: duplicate
closed: duplicate
Issue already reported, or changes included in a different PR
closed: non-issue
closed: non-issue
Not really a problem
closed: wontfix
closed: wontfix
We won't fix this issue, because it would be too difficult and/or isn't important enough to fix
code health
code health
improving internal code structure to make easier to maintain (sustainability)
documentation
documentation
additions or edits to user-facing documentation
done
done
Issues whose closing PR is done but not yet merged (pending test re-run ok)
enhancement
enhancement
new capability or improved behavior of existing capability
external
external
issue needs to be addressed elsewhere (submodule); issue here for the sake of project tracking
FATES API update
FATES API update
Changes to the FATES version that also REQUIRE an API change in CTSM
FATES
FATES
A change needed for FATES that doesn't require a FATES API update.
good first issue
good first issue
simple; good for first-time contributors
investigation
investigation
Needs to be verified and more investigation into what's going on.
modernization
modernization
E.g., for improving ability to perform on new computing architectures
next
next
this should get some attention in the next week or two. Normally each Thursday SE meeting.
non-bfb
non-bfb
Changes answers (incl. adding tests)
performance
performance
idea or PR to improve performance (e.g. throughput, memory)
PR status: awaiting review
PR status: awaiting review
Work on this PR is paused while waiting for review.
PR status: needs testing
PR status: needs testing
PR status: ready
PR status: ready
PR: this is ready to merge in, with all tests satisfactory and reviews complete
priority: high
priority: high
High priority to fix/merge soon, e.g., because it is a problem in important configurations
priority: Immediate
priority: Immediate
Highest priority, something that was unexpected
priority: low
priority: low
Background task that doesn't need to be done right away.
science
science
Enhancement to or bug impacting science
size: large
size: large
Large project that will take a few weeks or more