-
Notifications
You must be signed in to change notification settings - Fork 25
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
[r] Prepare for CRAN [long-term tracker] #1582
Comments
In my experience the CRAN_comments.md is a myth. I have never heard anyone from CRAN recommending or requesting it yet I heard repeatedly that whatever was written in it was ignored. To be best of my understanding it serves primarily for pre-release notekeeping. |
I took the liberty of co-assigning @aaronwolen and @mojaveazure who both have 'CRAN battle experience' too. |
@eddelbuettel what steps remain to bring this issue to closure? |
There was a bit of a sentiment recently that maybe CRAN release does not buy as all that that we don't already have with r-universe. Happy to chat off-line. |
Per internal discussion we will revisit this once TileDB-R has been removed as a dependency from TileDB-SOMA-R. See also #2406. |
Follow-on from #1567
R CMD check --as-cran
on r-release as a minimal layerR CMD check --as-cran
on r-devel (in docker, locally [ I keep it on Ubuntu ], rhub,win-builder(inapplicable, no Windows package), mac-builder (works, has cnake and git)R CMD check --use-valgrind
(and inspect*.Rout
files created) which currently errors and would lead to CRAN removal post-acceptanceThe text was updated successfully, but these errors were encountered: