Conversation
Contributor
|
@normanrz we just discussed this in the context of the OME meeting. It looks like the blosc-java version consumed in this PR was released from an in-progress branch/draft PR - scalableminds/blosc-java#3 Is there a plan to rationalise this so that we can track versions of the dependencies? |
Member
Author
|
The problem here is the release process of blosc-java, which is a bit too eager. We will fix that so that there are proper pull requests and tags for released. For zarr-java, we can think about whether you would have the resources to help maintain the repo in the form of approving PRs and greenlighting releases? |
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
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.
No description provided.