-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amends after CRAN feedback #184
Conversation
@pepaaran from the licensing point of view everything is ok. Makes sure to adjust your CRAN submission statement and the NEWS file according to the latest changes, including making the licensing more transparent. The CRAN submission statement in particular must include how you addressed all comments made in the previous rejection of the package (as with peer review in science). If we didn't address an issue it has to be explained why as well (the motivation must hold). Does this make sense? |
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #184 +/- ##
==========================================
- Coverage 75.68% 75.50% -0.19%
==========================================
Files 36 36
Lines 4175 4172 -3
==========================================
- Hits 3160 3150 -10
- Misses 1015 1022 +7
☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, looks good thanks
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
still looks good
/dontrun
statements from docs