Uploaded image for project: 'Apache Arrow'
  1. Apache Arrow
  2. ARROW-18345

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

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 11.0.0
    • R

    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!

      Attachments

        Issue Links

          Activity

            I've been keeping https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingRpackages up to date. The only thing not mentioned there is that I generally make a branch on my fork off of the release tag (apache-arrow-x.y.z) where I add/cherry-pick any extra commits we need for the CRAN release. Sometimes this is just deleting the line in the README with the badges to avoid spurious URL check failures.

            The other thing not mentioned there, now that I look at it, is doing reverse dependency checks.

            npr Neal Richardson added a comment - I've been keeping https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingRpackages up to date. The only thing not mentioned there is that I generally make a branch on my fork off of the release tag ( apache-arrow-x.y.z ) where I add/cherry-pick any extra commits we need for the CRAN release. Sometimes this is just deleting the line in the README with the badges to avoid spurious URL check failures. The other thing not mentioned there, now that I look at it, is doing reverse dependency checks.

            Issue resolved by pull request 14678
            https://github.com/apache/arrow/pull/14678

            paleolimbot Dewey Dunnington added a comment - Issue resolved by pull request 14678 https://github.com/apache/arrow/pull/14678
            rokm Rok Mihevc added a comment -

            This issue has been migrated to issue #33513 on GitHub. Please see the migration documentation for further details.

            rokm Rok Mihevc added a comment - This issue has been migrated to issue #33513 on GitHub. Please see the migration documentation for further details.

            People

              paleolimbot Dewey Dunnington
              paleolimbot Dewey Dunnington
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 21h 10m
                  21h 10m