Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[ MRG | doc | #15426 | KernelRidge, AgglomerativeClustering ] #15518

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

Closed
wants to merge 1 commit into from

Conversation

lotusea
Copy link

@lotusea lotusea commented Nov 2, 2019

Reference Issues/PRs

What does this implement/fix? Explain your changes.

Any other comments?

@eickenberg
Copy link
Contributor

Looks good to me formatwise pending CI

What is your strategy for obtaining these versions?

@lotusea
Copy link
Author

lotusea commented Nov 2, 2019

@eickenberg I did a git grep for "AgglomerativeClustering" and for "KernelRidge" and used the doc/whats_new/v*** as reference for version number.

@katarinaslama
Copy link
Contributor

This overall looks good per the change logs.

How do you know that version 0.16 for KernelRidge should be listed as "versionchanged" as opposed to "versionadded"?

@jnothman
Copy link
Member

jnothman commented Nov 3, 2019

Changed means that the behaviour was changed, not that a new feature was added

@rth rth added Needs work and removed Needs work labels Nov 3, 2019
@@ -661,6 +661,8 @@ class AgglomerativeClustering(ClusterMixin, BaseEstimator):

Read more in the :ref:`User Guide <hierarchical_clustering>`.

.. versionadded:: 0.15
Copy link
Member

Choose a reason for hiding this comment

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

linting fails because these should be spaces instead of tabs

@@ -36,6 +36,8 @@ class KernelRidge(MultiOutputMixin, RegressorMixin, BaseEstimator):

Read more in the :ref:`User Guide <kernel_ridge>`.

.. versionchanged:: 0.16
Copy link
Member

Choose a reason for hiding this comment

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

I think it only makes sense to report the versionadded as estimator behavior change rather frequently...

Copy link
Member

Choose a reason for hiding this comment

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

Changes in parameter semantics are worth noting... But they need detail

Base automatically changed from master to main January 22, 2021 10:51
@thomasjpfan
Copy link
Member

Closing based on #15426 (comment) where we concluded that we do not need to tag for versions < 0.18

@thomasjpfan thomasjpfan closed this Apr 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants