[MRG] DOC: Moves whats new entry on Pipeline's passthrough to 0.21 #12787
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
good point, maybe not? I don't have a strong opinion |
|
I'd personally rather not have whats_new entries for bug fixes and changes on unreleased features. Otherwise if we wanna be consistent, we'd end up with tons of whats_new entries for something like OPTICS, before it's even released. |
|
I don't think we need bug fix entry for unreleased features. I'll push directly. Thanks @thomasjpfan |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reference Issues/PRs
See also #12659
What does this implement/fix? Explain your changes.
Moves whats new entry about Pipeline's "passthrough" to 0.21.
Any other comments?
Since this is a bug fix for an unreleased feature, does this bug fix need a whats new entry?