-
-
Notifications
You must be signed in to change notification settings - Fork 26.2k
[MRG] Release 0.21.3 #14188
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
[MRG] Release 0.21.3 #14188
Conversation
What do others think of this as a release? Is early July okay? Please help identify DOC and maint changes that should be pulled into 0.21.X. |
Good idea! Fixing failing tests in #14192 would help with this. |
BTW, do we still intend to release 0.20.4? I keep confusing that tag with 0.21.3 and I might not be the only one. Is there any critical fixes worth backporting to the last version that supports Python 2.7? |
We can release 0.20.4 to handle the regressions fixed there:
https://github.com/scikit-learn/scikit-learn/milestone/30?closed=1. The
StratifiedKFold issue is nasty as a silent bug, but otherwise I'm
ambivalent.
|
+1 . We could also synchronize joblib that has bugs in the versions shipped in 0.20.3. |
I'll try to propose some workaround for #12676 (test_omp_cv fails with MKL and AVX-512) tomorrow. |
Wait I hadn't seen the StratifiedKFold bug. That means |
* updated class_weight explanation * glossary_class_weight
…4149) in order to fix warnings
…4144) * fix convergence warnings * fix convergence warnings * PEP8 * PEP8 * Fix Convergence Warning by changing the Optimization Algorithm * PEP8 * Fixed Future Warnings by explicitly defining n_estimators. * PEP8 * deleted all * Fixed Convergence Warnings * removed changes on unrelated examples * add comment and with statement * PEP8 * context manager fix * fixed indentation * PEP8 * flake8
I'll throw in some documentation enhancements for good measure. |
Thanks. I didn't notice that change in master but I adopted master's
changes in a merge resolution.
|
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.
need to clean up what's new, otherwise LGTM
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.
You're right, I landed up with duplicated change logs
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.
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 #14500 is merged and backported here.
This branch currently just includes scikit-learn/scikit-learn/milestone/30?closed=1 and scikit-learn/scikit-learn/milestone/34?closed=1.
So do we want to release 0.20.4 first, and then backport its what new so it would show up on the stable documentation?
Yes, I intended to do that, but it can work in either direction.
|
Building wheels at https://travis-ci.org/MacPython/scikit-learn-wheels/builds/564978538?utm_source=github_status&utm_medium=notification Checklist:
|
Glad that it is done. Thanks for making this release happen @jnothman ! |
No worries. Glad it is done!
|
To be merged without squashing.
I thought we should consider if 0.21.3 should be released at some point soon (early July). It's one month since 0.21.2 was released. This branch currently just includes https://github.com/scikit-learn/scikit-learn/milestone/30?closed=1 and https://github.com/scikit-learn/scikit-learn/milestone/34?closed=1. We should review documentation commits that should also be included.
The initial commit selection is: