[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16863402#comment-16863402 ] Wes McKinney commented on ARROW-3204: - Let this be closed when the package is finally on CRAN; it can't really be resolved until after the next Apache release has taken place anyway > [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 >Assignee: Neal Richardson >Priority: Critical > Labels: release > > 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758601#comment-16758601 ] Javier Luraschi commented on ARROW-3204: I don't see an issue for distributing into Debian/Fedora so I'll open one and link here, will also request help from d...@arrow.apache.org. > [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 > > 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747314#comment-16747314 ] Wes McKinney commented on ARROW-3204: - I'll keep attaching child issues to this issue that are required (or related, like setting up CI for Windows) as part of the testing and packaging process. If there is anything necessary that is not in the issue tracker already please create new issues > [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 > > 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747309#comment-16747309 ] Wes McKinney commented on ARROW-3204: - AFAIK no one from this community has been maintaining the Homebrew recipe. So that will obviously have to change so that updating the Homebrew recipe is part of the release management process. No one did anything wrong here I'm creating a sub-task about Homebrew and attaching it as a child of this issue > [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 > > 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747277#comment-16747277 ] Jeroen commented on ARROW-3204: --- The Homebrew lead maintainer has dropped arrow from homebrew because it isn't building: https://github.com/Homebrew/homebrew-core/commit/6cd7f61d2d07d5fd9f8747ea0f620169cc8a2434 . So this further complicates things for R bindings on MacOS. I am guessing that the build broke because the 0.11 tarball has been removed from the apache website, even though 0.12 hasn't even been announced yet? [https://www.apache.org/dist/arrow/] > [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 > > 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[
https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16745753#comment-16745753
]
Javier Luraschi commented on ARROW-3204:
A few folks working on R and Arrow got together today, we agree that the R
Arrow package should be in CRAN as soon as possible. However, this is likely to
take a few months since we have to first:
# Have an appropriate build process for Windows which Jeroen is leading, see
[rwinlib/arrow|[https://github.com/rwinlib/arrow].]
# Proper appveyor automation. The UrsaLabs team is planning to hire a build
engineer to help, in the meantime, Kirill might be able to help get this going
to make sure Jeroen's work does not regress as Arrow 0.13 gets developed.
# Have an appropriate build process for OS X.
# The Arrow libraries need to get distributed in the official Debian
repository to be allowed in CRAN. Wes mentioned that, Kouhei (hoping I got this
right), might be able to help the project navigate this in the next few months.
So, while we completely agree with you that is imperative that Arrow gets in
CRAN, in the meantime, we could still make use of Arrow in OS X and Linux using
the remotes package (or devtools) by installing the Arrow runtime first,
followed by:
{code:java}
remotes::install_github("apache/arrow", subdir = "r")
{code}
> [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
>
> 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16695522#comment-16695522 ] Hyukjin Kwon commented on ARROW-3204: - +100! I can't wait to use Arrow R API! > [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 > > 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)
[jira] [Commented] (ARROW-3204) [R] Release to CRAN
[ https://issues.apache.org/jira/browse/ARROW-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16609133#comment-16609133 ] Wes McKinney commented on ARROW-3204: - I agree that this software should be made available on CRAN. Because of GPL dependencies we (the Arrow PMC) may have to leave the actual distribution of binaries for this software to the R community to do as it wishes. We can develop the tools to assist with that here > [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 > > 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)
