-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[R] CRAN packaging checklist for version 13.0.0 #36802
Comments
TODO: follow-up on discussions in #36551 to see if we need to do anything difference for this release |
We'll need to cherry-pick the NEWS update into here: #36806 |
I ran the revdepchecks using dataversionrWith CRAN arrow
With local arrow
gbifdbWith CRAN arrow
With local arrow
nanoarrowWith CRAN arrow
With local arrow
pinsWith CRAN arrow
With local arrow
|
We should flag #34775 as a breaking change |
revdepcheck failures:
I've mentioned that we are planning to release to CRAN in 2 weeks from now (17th August) |
We need to also grab the missing NEWS items documentation: #37326 |
And this one so we don't fail on CRAN: #37387 |
I've also cherry-picked this into this branch as we were failing on R-devel: #37457 |
Done! |
Packaging checklist for CRAN release
For a high-level overview of the release process see the
Apache Arrow Release Management Guide.
Before the release candidate is cut
[R] CRAN packaging checklist for version X.X.X
and copy this checklist to the issue.urlchecker::url_check()
on the R directory at the release candidate.commit. Ignore any errors with badges as they will be removed in the CRAN release branch.
archery docker run r-revdepcheck
.Wait for the release candidate to be cut:
After release candidate has been cut
Optional: PRs for autobrew and rtools (release candidate)
Make pull requests into the autobrew and
rtools-packages repositories
used by the configure script on MacOS and Windows. These pull requests will
use the release candidate as the source.
the apache-arrow autobrew formula
to update the release version, SHA256 checksum of the release source file (which can be found in the same directory as the release source file), and any changes to dependencies and build steps that have changed in the
copy of the formula we have of that formula in the Arrow repo
the apache-arrow-static autobrew formula
to update the version, SHA, and any changes to dependencies and build steps that have changed in the
copy of the formula we have of that formula in the Arrow repo
autobrew script
to include any additions made to
r/tools/autobrew.
RTools PKGBUILD script
to reflect changes in
ci/PKGBUILD,
uncommenting the line that says "uncomment to test the rc".
Prepare and check the .tar.gz that will be released to CRAN.
git fetch upstream && git checkout release-X.X.X-rcXX && git clean -f -d
make build
. This copies Arrow C++ into tools/cpp, prunes someunnecessary components, and runs
R CMD build
to generate the source tarball.Because this will install the package, you will need to ensure that the version
of Arrow C++ available to the configure script is the same as the version
that is vendored into the R package (e.g., you may need to unset
ARROW_HOME
).devtools::check_built("arrow_X.X.X.tar.gz")
locallyarchery docker run r-revdepcheck
.Release vote
PRs for autobrew and rtools (official release)
Create new autobrew and r-windows PRs such that they use the release
instead of the release candidate:
Generate R package to submit to CRAN
on that commit.
were needed to fix CRAN-related submission issues identified in the above
steps.
urlchecker::url_check()
on the R directoryWIP: [R] Verify CRAN release-10.0.1-rc0
. Adda comment
@github-actions crossbow submit --group r
to run all R crossbowjobs against the CRAN-specific release branch.
make build
)Ensure linux binary packages are available:
https://apache.jfrog.io/ui/repos/tree/General/arrow/r
Check binary Arrow C++ distributions specific to the R package
and confirm (with Nic, who will automatically receive an email about the results) that the check is clean.
This step cannot be completed before Jeroen has put the binaries in the MinGW repository, i.e. here, here, and here.
and confirm that the check is clean
https://mac.r-project.org/macbuilder/results/1693354381-aed8fd0fff067774/
install.packages("arrow_X.X.X.tar.gz")
on Ubuntu and ensure that thehosted binaries are used
devtools::check_built("arrow_X.X.X.tar.gz")
locally one more time (for luck)CRAN submission
CRAN submit page
Wait for CRAN...
ci/scripts/PKGBUILD
,dev/tasks/homebrew-formulae/autobrew/apache-arrow.rb
,r/DESCRIPTION
, andr/NEWS.md
pkgdown::build_site(examples = FALSE, lazy = TRUE, install = FALSE)
and submit a PR to theasf-site
branch of the docs site with the contents ofr/docs/news/index.html
.r/pkgdown/assets/versions.json
, and update this on the theasf-site
branch of the docs site too.packaging process.
CRAN package page to reflect the
new version
The text was updated successfully, but these errors were encountered: