assignUser commented on code in PR #14678: URL: https://github.com/apache/arrow/pull/14678#discussion_r1034733753
########## r/PACKAGING.md: ########## @@ -0,0 +1,117 @@ + +<!--- + Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + + Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. +--> + +# Packaging checklist for CRAN release + +For full documentation of the steps in this checklist, see the +[Apache Arrow Release Management Guide](https://arrow.apache.org/docs/developers/release.html#post-release-tasks). + +- [ ] When a release candidate is created + [Create a GitHub issue](https://github.com/apache/arrow/issues/new/) + entitled `[R] CRAN release version X.X.X` and copy this checklist to the issue + +- [ ] Confirm that all + R-related [nightly tests and nightly packaging builds](https://lists.apache.org/[email protected]) from immediately before the RC was cut are passing. +- [ ] Check [current CRAN check results](https://cran.rstudio.org/web/checks/check_results_arrow.html) Review Comment: Sadly an initial clean check result can change later on due to changes to R-devel, changes to the test environments or updated dependencies, so it makes sense to check for any needed fixes before pushing a new release (not that CRAN wouldn't point those issues out with a "you have 2 weeks"-mail ...) -- 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]
