paleolimbot commented on code in PR #14678:
URL: https://github.com/apache/arrow/pull/14678#discussion_r1034949014
##########
docs/source/developers/release.rst:
##########
@@ -487,7 +487,39 @@ Be sure to go through on the following checklist:
:class-title: sd-fs-5
:class-container: sd-shadow-md
- TODO: Move from
https://cwiki.apache.org/confluence/display/ARROW/Release+Management+Guide#ReleaseManagementGuide-UpdatingRpackages
+ To publish the R package on CRAN, there are a few steps we need to do first
+ in order to ensure that binaries for Windows and macOS are available to
CRAN.
+ Jeroen Ooms <[email protected]> maintains several projects that build C++
+ dependencies for R packages for macOS and Windows. We test copies of these
+ same build scripts in our CI, and at release time, we need to send any
+ changes we have and update the versions/hashes upstream.
+
+ When the release candidate is made, make draft pull requests to each
+ repository using the rc, updating the version and SHA, as well as any cmake
+ build changes from the corresponding files in apache/arrow. Jeroen may
+ merge these PRs before the release vote passes, build the binary artifacts,
+ and publish them in the right places so that we can do pre-submission checks
+ (see below). After the release candidate vote passes, update these PRs
+ to point to the official (non-rc) URL and mark them as ready for review.
Review Comment:
I think they are embedded in the hombrew files (there are links to the
homebrew scripts in the checklist). I think there will be a number of specific
additions after we get through this release and I wonder if we could use the
release issue itself as a place to collect additions that would be useful?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
