[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neal Richardson updated ARROW-3204: ----------------------------------- Labels: release (was: ) > [R] Release to CRAN > ------------------- > > Key: ARROW-3204 > URL: https://issues.apache.org/jira/browse/ARROW-3204 > Project: Apache Arrow > Issue Type: New Feature > Components: R > Reporter: James Lamb > Priority: Major > Labels: release > Fix For: 0.14.0 > > > As of [ARROW-1325|https://issues.apache.org/jira/browse/ARROW-1325], the > project contains a minimal working R package that takes advantage of R's > built-in support for calling C++ code and uses Rcpp for added support. > Though the exact public interface of the package hasn't been developed yet > (so this issue may be running before we walk), one major feature in its > development will be release to [CRAN|https://cran.r-project.org/], the > official package repository for the R language. > Completing this story would mean: > * Getting source code to state where [R CMD > CHECK|https://www.r-bloggers.com/how-i-learned-to-stop-worrying-and-love-r-cmd-check/] > passes with 0 ERRORS, 0 WARNINGS, and 0 NOTES > * Setting up build process for source and precompiled binary packages (see > [data.table|https://github.com/Rdatatable/data.table] and > [XGBoost|https://github.com/dmlc/xgboost] as examples of packages that do > this) > * Submission to CRAN and acceptance of the first release > > Distribution via CRAN would be a much more natural fit for most R users' > workflows than the current build-from-source workflow, and comes with all the > other benefits of package managers (e.g. version pegging, easy distribution > of platform-specific binaries). -- This message was sent by Atlassian JIRA (v7.6.3#76005)