Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMerged 2.1.7 into master (just VERSION changes) #699
Merged
Conversation
failures are unrelated (I will submit those tiny fixes shortly to fix at least travis), and so ppl do not get confused (I need to instruct them not to pip install from master), I will merge this one |
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.
I guess just that master diverged from the release tag, that left VERSION stating that current master is 2.1.6 . Detected while observing installation from git master in our datalad travis setup:
https://travis-ci.org/datalad/datalad/jobs/308052470#L1012
This PR just merges 2.1.7 tag back into master, so also
git describe --tags
provides adequate information about current state of the affairs in master