-
Notifications
You must be signed in to change notification settings - Fork 3
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
Merge manuscript branch #72
Conversation
…vant tools did not exist at that time
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.
I'm not sure the manuscript itself needs to be included. What about just linking to the paper as suggested in #73?
I also wouldn't include the benchmark RDS files. Since they were long & difficult to generate, it may indeed to worth saving save somewhere though. I'm just not sure where. As release artifacts?
Said differently, I would just add the benchmarking scripts.
In any case, this PR will require changes in .Rbuildignore
before merging.
See #82 instead |
Now that the paper is published 🎉 we could merge this branch in the main one, right?
So the manuscript and benchmarks are all together with the package.
Is it necessarily distributed whenever people download the package?