-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
For release 2025.01.00
#102
Conversation
…_externals [feature] Expose stencil vertical domain to Frozen Stencil
Support for 4d Data
…reshold_override' into feature/multimodal_metric_threshold_override
…reshold_override' into feature/multimodal_metric_threshold_override
[QOL] Fix for boilerplate to work on GPU
Implemented `allreduce` & `Allreduce` for Communicator
* Fix typos * DaCeProgress: avoid double assignment of prefix * Add type hints/simplify kernel_theoretical_timing Adding type hints allowed to simplify `kernel_theoretical_timing`.
Refactor Quantity into a sub-directory
Hotfix for grid generation use of mpi operators
Removes hard-coded version numbers from `__init__` files.
Cleanup: `.gitignore` / `__version__` strings / bunch of typos
Hotfix to netcdf python version
Release candidate: `2025.01.00`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The commit list here and yesterday on the develop
branch, makes me think we ought to make squash-merge
the default for merging into develop
and main
. That way, in lieu of every commit of every branch, we would have only PR consolidated commits, easier for review of what we are moving in. And we could focus our effort on making sure the messages of those commits are readable and verbose enough.
For example - for this release there's 108 commits being merged in |
I agree with @FlorianDeconinck on the use of squash commits keeping only the relevant info from the actual merge/PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed with @FlorianDeconinck as well about squash merging
@FlorianDeconinck and @bensonr, I have now made squash merge the default method moving forward |
Description
This PR will bring the changes from
develop
into themain
branch for release2025.01.00
Checklist: