up version to 0.21.0 #2225
Merged
up version to 0.21.0 #2225
Conversation
This file contains 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
|
@nalimilan - CI passes cleanly except the known regex error on OSx nightly. |
quinnj
approved these changes
May 5, 2020
|
Thank you! Let us just wait for @nalimilan to approve (and we need to merge JuliaData/CSV.jl#602 and make a release of CSV.jl also to have everything in sync). |
|
@nalimilan is free to merge that PR and tag a new CSV release; so we can let him do all the synchronizing. (I'm happy to merge/tag as well if needed, just ping me on slack) |
|
This PR should be merged first, then I can make a release of DataFrames.jl, then CSV.jl needs to be updated (as it currently depends on DataFrames.jl also). Thank you! |
nalimilan
approved these changes
May 5, 2020
|
Thank you! |
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.
A final check before 0.21 release.
The plan is that ideally the next release is 1.0 and we do not include any breaking changes (the reality might turn out to be different).
What are key objectives to do after 0.21 release till 1.0 release:
I would plan that we shall make 1.0 release in 3 to 6 months from now (depending how the things progress and the user feedback).
What I also will do after the release:
Thank you for working on the package!