-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
DOC fix the changelog and group entries together #27421
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
Conversation
I think grouping things for Array API support makes sense. Though from a marketing point of view I think we should not call it "Array API support" but something like "GPU support" or something. Mostly this is a communication thing. Most people who work on this stuff know the plan (Array API for python, plugins for cython) but people not directly involved often bring up "yeah but array api won't work ..." because they seem to assume that all we are doing is adding Array API support. (This is mostly a side comment to start y'all brains thinking :D ) |
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.
Otherwise LGTM.
doc/whats_new/v1.4.rst
Outdated
- |Enhancement| :class:`preprocessing.TargetEncoder` now supports `target_type` | ||
'multiclass'. :pr:`26674` by :user:`Lucy Liu <lucyleeow>`. | ||
|
||
- |MajorFeature| :class:`preprocessing.MinMaxScaler` and |
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.
We should respect the standard label ordering MajorFeature > Feature > ... > Enhancement > Fix.
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 once the ordering of the entries is fixed.
The CI has failed because of a problem in |
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.
BTW, this is very hard to properly review:smirk:
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Co-authored-by: Olivier Grisel <olivier.grisel@ensta.org>
Fixing some issues seen in the changelog of 1.4.
Also grouped together PRs linked to support for sparse matrices.
I also think it could be meaningful to do the same for the Array-API if we think that we will have a rather wide support for the next release. I did not do it here. I would let @ogrisel @betatim to let me know what they think.