Skip to content
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

Release summary for release v2024.01.0 #8617

Merged
merged 6 commits into from
Jan 17, 2024
Merged

Conversation

TomNicholas
Copy link
Member

@TomNicholas TomNicholas commented Jan 17, 2024

Someone give this a thumbs up if it looks good

@TomNicholas TomNicholas added the Release Planning and tracking progress of releases label Jan 17, 2024
doc/whats-new.rst Outdated Show resolved Hide resolved
@TomNicholas
Copy link
Member Author

Thanks @kmuehlbauer !

@TomNicholas TomNicholas enabled auto-merge (squash) January 17, 2024 19:01
@TomNicholas TomNicholas merged commit 072f44c into pydata:main Jan 17, 2024
26 checks passed
Comment on lines +39 to +50
Note that some new compression filters needs plugins to be installed which may not be available in all netCDF distributions.
By `Markel García-Díez <https://github.com/markelg>`_. (:issue:`6929`, :pull:`7551`)
- Add :py:meth:`DataArray.cumulative` & :py:meth:`Dataset.cumulative` to compute
cumulative aggregations, such as ``sum``, along a dimension — for example
``da.cumulative('time').sum()``. This is similar to pandas' ``.expanding``,
and mostly equivalent to ``.cumsum`` methods, or to
:py:meth:`DataArray.rolling` with a window length equal to the dimension size.
By `Maximilian Roos <https://github.com/max-sixty>`_. (:pull:`8512`)
- Decode/Encode netCDF4 enums and store the enum definition in dataarrays' dtype metadata.
If multiple variables share the same enum in netCDF4, each dataarray will have its own
enum definition in their respective dtype metadata.
By `Abel Aoun <https://github.com/bzah>`_. (:issue:`8144`, :pull:`8147`)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm very late to the party, but note that the issue / pr links are after the user links, unlike our previous convention. @TomNicholas, should we fix that before the release?

Also, should we merge #8605 first? The fix for CI, as discussed today in the meeting, was to remove pint from the environment for now.

If you'd say yes to both, I can push the fix in #8605

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

note that the issue / pr links are after the user links, unlike our previous convention

Oh huh - looks like people are inconsistent with that in whats-new. I can fix that.

Also, should we merge #8605 first?

If that's ready to merge now then sure!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, it is. The tests just passed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Release Planning and tracking progress of releases
Projects
None yet
Development

Successfully merging this pull request may close these issues.

new release 2024.01.0
3 participants