Release 0.7.15 #99
Merged
Release 0.7.15 #99
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
|
We also need to bump the javadoc up to 0.7.15, and tag a release. I'm also going to start a bit of a project to increase the testing coverage. We've slipped a little in recent months. |
Collaborator
Author
|
@pabender do you know how to do that? |
Member
|
according to https://www.javadoc.io/ (which is where the badge comes from on the repo) It's supposed to happen automatically within 24 hours of a Maven Central upload. It appears @rhwood put the badge in place, so perhaps he can let us know if there is anything else we need to do to update the badge. |
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.
No description provided.