Remove obsolete config file #2141
Merged
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
Member
|
I think this change warrants a new major version. What do you think? |
Member
Author
|
Yeah, or it might be 5.2.0 as it's not breaking, it just removes the obsolete |
Member
Author
|
I was considering to change the milestone from 5.1.4 to 5.2.0 as there are a lot of issues/changes |
Member
|
Yeah, agreed. As you write, the deprecation warning has been there since v4, so let's bump to 5.2 and get rid of it. |
asbjornu
approved these changes
Feb 26, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As the legacy configuration file was deprecated long time ago, I think in version 4.x we're removing it in this version