Skip to content
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

Submit to CRAN #13

Open
rguliev opened this issue Jun 3, 2016 · 1 comment
Open

Submit to CRAN #13

rguliev opened this issue Jun 3, 2016 · 1 comment

Comments

@rguliev
Copy link
Collaborator

rguliev commented Jun 3, 2016

In GitLab by @bryanhanson on Jun 3, 2016, 03:24

By the end of the summer, we should be able to submit unmixR to CRAN.

@rguliev
Copy link
Collaborator Author

rguliev commented Aug 7, 2017

In GitLab by @bryanhanson on Aug 7, 2017, 15:16

Here are the steps to get (almost) ready for CRAN:

  1. Move to new branch CRAN
  2. Remove large files (from testing) in folder inst
  3. Move testthat instances to the typical place so hacked functions are not needed for checking (which can't pass CRAN checks). See 40-Fix reporter #44
  4. Add [nojss] to vignette for the time being -- removes JSS header/footers
  5. See what's left in terms of check issues.
  6. Also, run the package by win-builder and rhub to check multiple platforms.

Let me know if you want me to proceed. It's easy enough to undo #44 but adding that back will be tough once branch CRAN is merged back into devel_2017 or master (but we have to pass CRAN checks somehow).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants