[
https://issues.apache.org/jira/browse/ARROW-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated ARROW-18345:
-----------------------------------
Labels: pull-request-available (was: )
> [R] Create a CRAN-specific packaging checklist that lives in the R package
> directory
> -------------------------------------------------------------------------------------
>
> Key: ARROW-18345
> URL: https://issues.apache.org/jira/browse/ARROW-18345
> Project: Apache Arrow
> Issue Type: Improvement
> Components: R
> Reporter: Dewey Dunnington
> Assignee: Dewey Dunnington
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Like other packaging tasks, the CRAN packaging task (which is concerned with
> making sure the R package from the Arrow release complies with CRAN policies)
> for the R package is slightly different than the overall Arrow release task
> for the R package. For example, we often push patch-patch releases if the
> two-week window we get to "safely retain the package on CRAN" does not line
> up with a release vote. [~npr] has heroically been doing this for a long
> time, and while he has equally heroically volunteered to keep doing it, I am
> hoping to process of codifying this somewhere in the R repo will help a wider
> set of contributors understand the process (even if it was already documented
> elsewhere!).
> [~stephhazlitt] and I use {{usethis::use_release_issue()}} to manage our
> personal R package releases, and I'm wondering if creating a similar function
> or markdown template would help here.
> I'm happy to start the process of putting a PR up for discussion!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
