[ARROW-18345] [R] Create a CRAN-specific packaging checklist that lives in the R package directory

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 11.0.0
• Component/s: R
• Labels: pull-request-available
• External issue URL: https://github.com/apache/arrow/issues/33513
• Assignee: Dewey Dunnington
• Reporter: Dewey Dunnington
• Created: 16/Nov/22 15:01
• Updated: 11/Jan/23 11:59
• Resolved: 09/Dec/22 18:29

Description

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!

Issue Links

• links to: GitHub Pull Request #14678